Fix links to ERC721

Author: sullof

ERCS/erc-7656.md

@@ -136,7 +136,7 @@ or an account interface or both. This flexibility makes existing account contrac
 
 The technical foundation of [ERC-7656](./eip-7656.md) centers on the extension and generalization of contract types that can be associated with NFTs. This approach was chosen to address specific limitations and opportunities identified in the design and application of NFT-linked contracts. Key technical decisions in this proposal include:
 
-- **Addressing ERC Proliferation and Contract Size Limitations**: The increasing number of ERC proposals extending the ERC-721 standard has led to complexity and potential confusion within the developer community. Since smart contracts have size limitations, incorporating multiple extensions into a single contract can become impractical or even impossible. [ERC-7656](./eip-7656.md) offers a solution by enabling the deployment of services that extend standard ERC-721 NFTs without requiring modifications to the ERC-721 standard itself. For example, instead of creating new ERCs to associate real-world assets with NFTs, developers can deploy specialized smart contracts owned by NFTs to add these features. This approach allows NFTs to seamlessly expand their capabilities while maintaining compliance with the existing ERC-721 standard, promoting a more efficient and modular development process.
+- **Addressing ERC Proliferation and Contract Size Limitations**: The increasing number of ERC proposals extending the [ERC-721](./eip-721.md) standard has led to complexity and potential confusion within the developer community. Since smart contracts have size limitations, incorporating multiple extensions into a single contract can become impractical or even impossible. [ERC-7656](./eip-7656.md) offers a solution by enabling the deployment of services that extend standard [ERC-721](./eip-721.md) NFTs without requiring modifications to the [ERC-721](./eip-721.md) standard itself. For example, instead of creating new ERCs to associate real-world assets with NFTs, developers can deploy specialized smart contracts owned by NFTs to add these features. This approach allows NFTs to seamlessly expand their capabilities while maintaining compliance with the existing [ERC-721](./eip-721.md) standard, promoting a more efficient and modular development process.
 
 - **Generic Function/Event Names**: The choice to adopt a generic naming convention for functions, errors, and events is deliberate. This design decision enables the [ERC-7656](./eip-7656.md) registry to support a wide array of contract types beyond mere accounts. By not prescribing specific roles or functionalities, we allow for greater innovation and flexibility in the types of applications that can be built on this standard. This also simplifies the interface and makes it more adaptable to various use cases.