docs: fix order of steps for ERC20 base tokens (#205)

minor fix for custom ERC20 token steps

content/10.zk-stack/20.running-a-zk-chain/30.custom-base-tokens.md

@@ -16,6 +16,11 @@ For now, you have the ability to add any tokens to the allowlist in your local e
 The overall flow for setting up a local chain with a custom ERC20 base token looks like the following:
 
 1. Deploy an ERC20 token to the L1.
+1. Create your new chain that uses the ERC20 token and set it as the default.
+    - When you set up your chain, you will be asked for the nominator and denominator for your base token.
+    - The base token nominator and denominator are used to define the relationship of the base token price with ETH.
+    - For example, if you set the nominator to 20 and the denominator to 1, together the relation is 20/1.
+    This would mean that 20 tokens would be given the equivalent value as 1 ETH for gas.
 1. Send ERC20 tokens to both the ecosystem and chain governor addresses on the L1.
     - You can find the addresses for the governor in `<YOUR_ECOSYSTEM_DIRECTORY>/configs/wallets.yaml`
     and `<YOUR_ECOSYSTEM_DIRECTORY>/chains/<YOUR_CHAIN_NAME>/configs/wallets.yaml` under `governor`.
@@ -29,11 +34,6 @@ The overall flow for setting up a local chain with a custom ERC20 base token loo
     --gas-price 30000000000
     ```
 
-1. Create your new chain that uses the ERC20 token and set it as the default.
-    - When you set up your chain, you will be asked for the nominator and denominator for your base token.
-    - The base token nominator and denominator are used to define the relationship of the base token price with ETH.
-    - For example, if you set the nominator to 20 and the denominator to 1, together the relation is 20/1.
-    This would mean that 20 tokens would be given the equivalent value as 1 ETH for gas.
 1. Initialize the new chain in the ecosystem.
 1. Bridge tokens from the L1 to your new chain.
     - You can use ZKsync CLI to bridge the tokens: