Clarify when to use ENSIP-11 (#240)

ensdomains · May 29, 2024 · feb00d8 · feb00d8
1 parent 02b90b7
commit feb00d8
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/web/resolution.mdx b/docs/web/resolution.mdx
@@ -141,7 +141,7 @@ To learn what happens under the hood when you do a forward lookup, read the [res
 ENS Names aren't just limited to storing Ethereum addresses.
 Any blockchain address (BTC, LTC, SOL, etc.) can be queried by [SLIP-0044](https://github.com/satoshilabs/slips/blob/master/slip-0044.md) coin type or a value derived from an EVM Chain ID (specified in [ENSIP-11](/ensip/11)). This includes Ethereum L2 networks such as OP Mainnet and Base.
 
-For EVM Chains, always use its [ENSIP-11](/ensip/11) coin type, irrespective of being included in SLIP-0044 (like Ether Classic).
+For EVM Chains besides Mainnet Ethereum, always use its [ENSIP-11](/ensip/11) coin type, irrespective of being included in SLIP-0044 (like Ether Classic).
 
 The standardization of multichain addresses was first introduced in [ENSIP-9](/ensip/9), and also [EIP-2304](https://eips.ethereum.org/EIPS/eip-2304).