mv eip-20 link

EIPS/eip-6909.md

@@ -322,7 +322,7 @@ MUST be logged when the `allowance` is set by an `owner`.
 
 ### Granular Approvals
 
-While the "operator model" from the ERC-1155 standard allows an account to set another account as an operator, giving full permissions to transfer any amount of any token id on behalf of the owner, this may not always be the desired permission scheme. The "allowance model" from ERC-20 allows an account to set an explicit amount of the token that another account can spend on the owner's behalf. This standard requires both be implemented, with the only modification being to the "allowance model" where the token id must be specified as well. This allows an account to grant specific approvals to specific token ids, infinite approvals to specific token ids, or infinite approvals to all token ids. If an account is set as an operator, the allowance SHOULD NOT be decreased when tokens are transferred on behalf of the owner.
+While the "operator model" from the ERC-1155 standard allows an account to set another account as an operator, giving full permissions to transfer any amount of any token id on behalf of the owner, this may not always be the desired permission scheme. The "allowance model" from [ERC-20](./eip-20.md) allows an account to set an explicit amount of the token that another account can spend on the owner's behalf. This standard requires both be implemented, with the only modification being to the "allowance model" where the token id must be specified as well. This allows an account to grant specific approvals to specific token ids, infinite approvals to specific token ids, or infinite approvals to all token ids. If an account is set as an operator, the allowance SHOULD NOT be decreased when tokens are transferred on behalf of the owner.
 
 ### Removal of Batching
 
@@ -423,7 +423,7 @@ The metadata specification closely follows that of the ERC-721 JSON schema.
 
 ## Backwards Compatibility
 
-This is not backwards compatible with ERC-1155 as some methods are removed. however, wrappers can be implemented for the [ERC-20](./eip-20.md), ERC-721, and ERC-1155 standards.
+This is not backwards compatible with ERC-1155 as some methods are removed. however, wrappers can be implemented for the ERC-20, ERC-721, and ERC-1155 standards.
 
 ## Reference Implementation