docs: address feedback

content/tutorials/custom-zk-chain/10.index.md

@@ -168,18 +168,18 @@ To summarize, the `init` command:
 - Deploys a paymaster contract and some test ERC20 contracts to use for development.
 
 You can find the paymaster contract deployed to your chain in the `zksync-era` repo in `contracts/l2-contracts/contracts/TestnetPaymaster.sol`,
-and the deployed address inside `my_elastic_chain/chains/zk_chain_1/configs/contracts.yaml` at `l2:testnet_paymaster_addr`.
+and the deployed address inside `<my_elastic_chain>/chains/zk_chain_1/configs/contracts.yaml` at `l2:testnet_paymaster_addr`.
 
-For the ERC20 contracts, you can find the deployed addresses inside `my_elastic_chain/configs/erc20.yaml`.
+For the ERC20 contracts, you can find the deployed addresses inside `<my_elastic_chain>/configs/erc20.yaml`.
 
 ### Understanding the chain configs
 
 Running the `init` command will also modify your chain configuration files in the ecosystem folder.
 
-The main configuration file for `zk_chain_1` can be found in `my_elastic_chain/chains/zk_chain_1/ZkStack.yaml`.
+The main configuration file for `zk_chain_1` can be found in `<my_elastic_chain>/chains/zk_chain_1/ZkStack.yaml`.
 It contains the most basic configurations for the chain.
 
-Inside `my_elastic_chain/chains/zk_chain_1/configs`, you can find six more configuration files:
+Inside `<my_elastic_chain>/chains/zk_chain_1/configs`, you can find six more configuration files:
 
 1. `contracts.yaml`: configurations for all the L1 & L2 contracts.
 1. `external_node.yaml`: configurations for the chain's node server.

content/tutorials/custom-zk-chain/20.customizing-your-chain.md

@@ -227,10 +227,10 @@ For testing purposes, we'll just use a 1:1 ratio.
 Now that you have some tokens and created a new chain,
 the next step is to send some to each of the governor's addresses for the ecosystem and chain on the L1.
 This will allow you to register and deploy your chain, and deploy the paymaster.
-For the _ecosystem governor_, you can find the address in `my_elastic_chain/configs/wallets.yaml` under `governor`.
+For the _ecosystem governor_, you can find the address in `<my_elastic_chain>/configs/wallets.yaml` under `governor`.
 
 The second governor address you need to fund is for the _chain governor_.
-The chain governor address can be found in `my_elastic_chain/chains/custom_zk_chain/configs/wallets.yaml` also under `governor`.
+The chain governor address can be found in `<my_elastic_chain>/chains/custom_zk_chain/configs/wallets.yaml` also under `governor`.
 
 Run the command below **twice** (once for each governor address) to use `cast` to transfer some of your ERC20 tokens to the governor's address on the L1.
 
@@ -252,6 +252,10 @@ cast balance --erc20 <0xYOUR_TOKEN_ADDRESS> \
 
 ### Initializing the chain
 
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+Make sure the server for `zk_chain_1` that you started in the previous section is shut down.
+::
+
 Next, initialize the chain in the ecosystem with the command below, and select the default options for the prompts.
 
 ```bash
@@ -381,8 +385,8 @@ To restart the ecosystem and run your custom ZK chain again, follow the steps be
 
 1. In the ecosystem folder, run `zk_inception containers`.
 1. Redeploy your ERC20 contract to the L1.
-1. Update the base token address in `my_elastic_chain/chains/custom_zk_chain/configs/contracts.yaml` under `l1.base_token_addr` and in
-  `my_elastic_chain/chains/custom_zk_chain/ZkStack.yaml` under `base_token.address`.
+1. Update the base token address in `<my_elastic_chain>/chains/custom_zk_chain/configs/contracts.yaml` under `l1.base_token_addr` and in
+  `<my_elastic_chain>/chains/custom_zk_chain/ZkStack.yaml` under `base_token.address`.
 1. Send ERC20 tokens to both of the ecosystem and chain governor addresses.
 1. Initialize the ecosystem with `zk_inception ecosystem init --dev`.
 1. Start the chain server with `zk_inception server`.