update

docs/maintain/wasp/v1.0.0-rc.6/docs/how-tos/running-an-access-node.md

@@ -63,14 +63,14 @@ You can then download the historical state using the following command (this wil
 <Tabs groupId="network" queryString>
 <TabItem value="shimmer" label="ShimmerEVM">
 
-```
+```sh
 wget https://files.shimmer.network/dbs/wasp/latest-wasp_chains_wal.tgz -O - | tar xzv -C data/wasp
 ```
 
 </TabItem>
 <TabItem value="shimmer_testnet" label="ShimmerEVM Testnet">
 
-```
+```sh
 wget https://files.testnet.shimmer.network/dbs/wasp/latest-wasp_chains_wal.tgz -O - | tar xzv -C data/wasp
 ```
 
@@ -95,67 +95,82 @@ You can check the sync status by following the logs with `docker logs -f hornet`
 
 ## Download Wasp-Cli
 
-You can download and extract the Wasp-Cli that matches your Wasp version using the following command:
+You can download a Wasp-Cli that matches your Wasp version from the [Wasp releases](https://github.com/iotaledger/wasp/releases).
+You can use a command like this to download the Wasp-Cli:
 
-```
+```sh
 curl -sL https://github.com/iotaledger/wasp/releases/download/v1.0.3/wasp-cli_1.0.3_Linux_x86_64.tar.gz | tar xzv
 ```
 
 ## Use Wasp-Cli to Obtain Peering Info
 
 Change directory into the newly-downloaded `wasp-cli` directory:
 
-```
+```sh
 cd wasp-cli_1.0.3_Linux_x86_64/
 ```
 
 ## Set the L1 API Address
 
+Set the L1 API address. You can set it to what you configured as `NODE_HOST` in the `.env` file
+
 ```sh
 ./wasp-cli set l1.apiaddress {NODE_HOST}
 ```
 
 ## Set Wasp API Address
 
+Set the WASP API address. It is your configured `NODE_HOST` and the `/wasp/api` path.
+
 ```sh
 ./wasp-cli wasp add my-node {NODE_HOST}/wasp/api
 ```
 
 ## Login
 
+Login to wasp using your credentials. You can update your current credentials or add new ones in the wasp dashboard.
+
 ```sh
 ./wasp-cli login
 ```
-```sh Output
+```sh title=Output
 Username: wasp
 Password: (default is wasp)
 Successfully authenticated
 ```
 
 ## Obtain Peering Info
+
+Get your peering info which you will need to share with your peers:
+
 ```sh
 ./wasp-cli peering info
 ```
-```sh Output
+```sh title=Output
 PubKey: 0x20a56daa0b5e86b196c37f802089a2b6007a655a12337d287f7313a214af2ec0
 PeeringURL: 0.0.0.0:4000
 ```
+
 Please note the PubKey: 0x20a56daa0b5e86b196c37f802089a2b6007a655a12337d287f7313a214af2ec0 output.
-Send it together with your Ipv4 to node operators that you want to peer with.
+Send it together with your domain/IP to node operators that you want to peer with.
 
 ## Wait for the other party to peer
 
-… wait …
+Wait until peer added you as trusted and access peer.
 
 ## Use wasp-cli to add nodes as peers
 
+Now you can add your peer as trusted peer.
+
 ```sh
-./wasp-cli peering trust peer1 <pubkey> <URL>
-./wasp-cli peering trust peer2 <pubkey> <URL>
+./wasp-cli peering trust peer1 <pubkey> <URL>:<PORT>
+./wasp-cli peering trust peer2 <pubkey> <URL>:<PORT>
 ```
 
 ## Add Chain
 
+Add the chain with its chain id and name:
+
 <Tabs groupId="network" queryString>
 <TabItem value="shimmer" label="ShimmerEVM">
 
@@ -175,6 +190,8 @@ Send it together with your Ipv4 to node operators that you want to peer with.
 
 ## Activate
 
+Actiave the chain using its name:
+
 
 <Tabs groupId="network" queryString>
 <TabItem value="shimmer" label="ShimmerEVM">
@@ -195,6 +212,14 @@ Send it together with your Ipv4 to node operators that you want to peer with.
 
 ## Add Peers as Access Nodes of the Chain
 
+Add the peers as access nodes.
+
+:::info
+
+This is normally only needed for peers that you plan to add as access nodes to your own node
+
+:::
+
 ```sh
 ./wasp-cli chain access-nodes add --peers=peer1,peer2
 ```