swap links

docs/5.advanced/6.evm-compatible.md

@@ -32,22 +32,19 @@ datasources:
 
 Default values here are for Ethereum mainnet and Alchemy node provider. To configure datasources for other networks, you need to change URLs and API keys. You can do it in the config file directly, but it's better to use environment variables. Check the `deploy/.env.default` file in your project directory; it contains all the variables used in config.
 
-### Subsquid Network
+### [evm.subsquid](../3.datasources/4.evm_subsquid.md)
 
-[evm.subsquid](../3.datasources/4.evm_subsquid.md) is where DipDup gets historical data from. It's the only datasource required to operate. If your favorite blockchain is on this page, it means that Subsquid Network has historical data for it.
+Subsquid Network is where DipDup gets historical data from. It's the only datasource required to operate. If your favorite blockchain is on this page, it means that Subsquid has historical data for it.
 
-### Etherscan
+### [abi.etherscan](../3.datasources/1.abi_etherscan.md)
 
-[abi.etherscan](../3.datasources/1.abi_etherscan.md) is a source of contract ABIs, which are used to generate types for the indexer.
+Etherscan is a source of contract ABIs, which are used to generate types for the indexer. Many explorers have Etherscan-like API which could be used to retrieve ABIs. You can get a URL for it in the table below. Please note, that some Etherscan-like explorers require an API key, which you can get on their website.
 
-Many explorers have Etherscan-like API and could be used to retrieve ABIs for further types generating using `abi.etherscan` datasource.
-You can get a URL for it in the table for your network, for some Etherscan-like explorers you will also need an API key.
+"🔴 no API" in the table below means we couldn't find an explorer with an Etherscan-like API for this network. You need to obtain contract ABI JSON somewhere and put it to the `abi/<typename>/abi.json` path. Don't forget to run `dipdup init` after that to generate all necessary types.
 
-"🔴 no API" in the table below means we couldn't find an explorer with Etherscan-like API for this network. You need to obtain contract ABI JSON somewhere and put it to the `abi/<typename>/abi.json` path. Don't forget to run `dipdup init` after that to generate all necessary types.
+### [evm.node](../3.datasources/3.evm_node.md)
 
-### EVM nodes
-
-[evm.node](../3.datasources/3.evm_node.md) datasource can be used to fetch recent data not yet in Subsquid Network. API methods could vary a lot across different networks, but DipDup only uses a few of them, so most of the nodes will work.
+EVM node datasource can be used to fetch recent data not yet in Subsquid Network. API methods could vary a lot across different networks, but DipDup only uses a few of them, so most of the nodes will work.
 
 WebSocket URL can be specified to get real-time updates. This option can save you some requests to the node, but otherwise, it's not required. If DipDup doesn't work with the EVM node in WebSocket mode, it's marked as "🟡 HTTP only" in the table below.