From dd10aaf094d7c3b0b75c9269d27e9238647e48c1 Mon Sep 17 00:00:00 2001
From: Ryan Ghods <ryan@ryanio.com>
Date: Thu, 26 Oct 2023 10:28:28 -0700
Subject: [PATCH] fix eip -> erc links

---
 ERCS/erc-7498.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/ERCS/erc-7498.md b/ERCS/erc-7498.md
index 45549411b60..ded55720003 100644
--- a/ERCS/erc-7498.md
+++ b/ERCS/erc-7498.md
@@ -13,7 +13,7 @@ requires: 165, 712, 721, 1155, 1271
 
 ## Abstract
 
-This specification introduces a new interface that extends [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md) to enable the discovery and use of onchain and offchain redeemables for NFTs.
+This specification introduces a new interface that extends [ERC-721](./erc-721.md) and [ERC-1155](./erc-1155.md) to enable the discovery and use of onchain and offchain redeemables for NFTs.
 
 ## Motivation
 
@@ -28,7 +28,7 @@ Creators frequently use NFTs to create redeemable entitlements for digital and p
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.
 
-The token MUST have the following interface and MUST return `true` for [ERC-165](./eip-165.md) supportsInterface for `0x1ac61e13`, the 4 byte interfaceId of the below.
+The token MUST have the following interface and MUST return `true` for [ERC-165](./erc-165.md) supportsInterface for `0x1ac61e13`, the 4 byte interfaceId of the below.
 
 ```solidity
 interface IERC7501 {
@@ -126,7 +126,7 @@ Including trait redemptions is optional, but if the token would like to enable t
 
 ### Signer
 
-A signer MAY be specified to provide a signature to process the redemption. If the signer is not the null address, the signature MUST recover to the signer address via [EIP-712](./eip-712.md) or [ERC-1271](./eip-1271.md).
+A signer MAY be specified to provide a signature to process the redemption. If the signer is not the null address, the signature MUST recover to the signer address via [EIP-712](https://eips.ethereum.org/EIPS/eip-712) or [ERC-1271](./erc-1271.md).
 
 The EIP-712 struct for signing MUST be as follows: `SignedRedeem(address owner,uint256[] considerationTokenIds,uint256[] traitRedemptionTokenIds,uint256 campaignId,uint256 requirementsIndex, bytes32 redemptionHash, uint256 salt)"`
 
@@ -305,11 +305,11 @@ As a new EIP, no backwards compatibility issues are present.
 
 ## Test Cases
 
-Authors have included Foundry tests covering functionality of the specification in the [assets folder](../assets/eip-7498/ERC721ShipyardRedeemable.t.sol).
+Authors have included Foundry tests covering functionality of the specification in the [assets folder](../assets/erc-7498/ERC721ShipyardRedeemable.t.sol).
 
 ## Reference Implementation
 
-Authors have included reference implementations of the specification in the [assets folder](../assets/eip-7498/ERC7498NFTRedeemables.sol).
+Authors have included reference implementations of the specification in the [assets folder](../assets/erc-7498/ERC7498NFTRedeemables.sol).
 
 ## Security Considerations