fix eip->erc

frangio · frangio · commit 95421031b004 · 2024-12-14T14:47:46.000-03:00
diff --git a/EIPS/eip-7702.md b/EIPS/eip-7702.md
@@ -254,7 +254,7 @@ A related issue is that an EOA's nonce maybe incremented more than once per tran
 
 ### Storage management
 
-In order to simplify the migration of an account from one delegate contract to another, it's important for these contracts to use storage in a way that avoids accidental collisions among them. For example, using [EIP-7201](./eip-7201.md) a contract may root its storage layout at a slot dependent on a unique identifier. To help with this, smart contract languages may provide a way of re-rooting the entire storage layout of an existing contract implementation.
+In order to simplify the migration of an account from one delegate contract to another, it's important for these contracts to use storage in a way that avoids accidental collisions among them. For example, using [ERC-7201](./erc-7201.md) a contract may root its storage layout at a slot dependent on a unique identifier. To help with this, smart contract languages may provide a way of re-rooting the entire storage layout of an existing contract implementation.
 
 Changing an account's delegation is a security-critical operation that should not be done lightly, especially if the newly delegated code is not purposely designed and tested as an upgrade to the old one. If all contracts previously delegated to by the account used the approach described above, a migration should not cause any issues. However, if there is any doubt, it is recommended to first clear all account storage, an operation that is not natively offered by the protocol but that a special-purpose delegate contract can be designed to implement.
 
