docs: minor fixes and feedback

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

@@ -51,7 +51,8 @@ Make sure to have the Docker daemon running.
 ::
 
 You will be prompted with a series of options to customize your ecosystem and generate a new chain within the ecosystem.
-For this tutorial, use the options shown below:
+For this tutorial, use the options shown below.
+If you choose different names for your ecosystem or chain, remember to update the names in the commands later on.
 
 ```bash
 $ zk_inception ecosystem create
@@ -184,8 +185,8 @@ Inside `my_elastic_chain/chains/zk_chain_1/configs`, you can find six more confi
 1. `secrets.yaml`: secrets that are individual for every chain.
 1. `wallets.yaml`: all wallets that you are using for this chain.
 
-::callout{icon="i-heroicons-light-bulb"}
-Never commit your private keys or sensitive secrets to a public repository!
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+Never commit your private keys or sensitive secrets to a public repository.
 ::
 
 ### Starting the chain server
@@ -203,6 +204,12 @@ With this, your L1 chain should be running at port `8545`, and the `zk_chain_1`
 Because you chose to use a local reth node for your L1 and selected ETH as the base asset,
 you have access to several rich wallets on the L1 that you can use to bridge ETH to `zk_chain_1`.
 
+You can find a full list of rich wallet addresses and their private keys in the [ZKsync docs](https://docs.zksync.io/build/test-and-debug/in-memory-node#pre-configured-rich-wallets).
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+Never use these wallets in production or send real funds to them.
+::
+
 Open a new terminal and run the command below to bridge some ETH to `zk_chain_1` using the `zksync-cli`:
 
 ```bash
@@ -217,8 +224,6 @@ For testing purposes, we'll use one of the rich wallets as both the sender and r
 ? Recipient address on L2 0x36615Cf349d7F6344891B1e7CA7C72883F5dc049
 ```
 
-You can find a full list of rich wallet addresses and their private keys in the [ZKsync docs](https://docs.zksync.io/build/test-and-debug/in-memory-node#pre-configured-rich-wallets).
-
 To see that it worked, let's check the balance of that address on `zk_chain_1`:
 
 ```bash

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

@@ -174,7 +174,7 @@ To verify that this worked, check the balance of the governor's address:
 
 ```bash
 cast balance --erc20 <0xYOUR_TOKEN_ADDRESS> \
-<0x_YOUR_GOVERNOR_ADDRESS> \ 
+<0x_YOUR_GOVERNOR_ADDRESS> \
 --rpc-url http://localhost:8545
 ```
 
@@ -239,7 +239,7 @@ Next, initialize the chain in the ecosystem with:
 zk_inception chain init
 ```
 
-This time select *no* for the option to deploy a paymaster contract.
+This time select *no* for the option to deploy a paymaster contract in order to avoid having to fund another address with your ERC20 base token.
 Use the default answers for all other prompts.
 
 Now that the chain is initialized, you can start the chain server:
@@ -270,7 +270,7 @@ npx zksync-cli bridge deposit --token <0x_YOUR_TOKEN_ADDRESS> \
 To verify that this worked, let's check the new balance of our address on the L2 chain:
 
 ```bash
-zksync-cli wallet balance \
+npx zksync-cli wallet balance \
 --address 0x36615Cf349d7F6344891B1e7CA7C72883F5dc049 \
 --rpc http://localhost:3050
 ```