DAL baker tutorial updates

docs/tutorials/join-dal-baker/get-octez.md

@@ -2,7 +2,7 @@
 title: "Step 1: Get a Weeklynet-compatible Octez version"
 authors: Tezos core developers
 last_update:
-  date: 23 January 2024
+  date: 14 February 2024
 ---
 
 The Weeklynet test network restarts every Wednesday at 0h UTC, and for most of its lifetime (from level 512) it runs a development version of the Tezos protocol, called Alpha, which is not part of any released version of Octez.
@@ -40,5 +40,13 @@ This endpoint also changes each time the network is reset.
    octez-client -E https://rpc.weeklynet-2024-01-17.teztnets.com config init
    ```
 
+1. Optional: Hide the network warning message by running this command:
+
+   ```bash
+   export TEZOS_CLIENT_UNSAFE_DISABLE_DISCLAIMER=y
+   ```
+
+   This command suppresses the message that your instance of the Octez client is not using Mainnet.
+
 Now you have the Octez client and node configured to work with Weeklynet.
 The next step is to start an Octez node; continue to [Step 2: Run an Octez node on Weeklynet](./run-node).

docs/tutorials/join-dal-baker/prepare-account.md

@@ -2,64 +2,92 @@
 title: "Step 3: Set up a baker account on Weeklynet"
 authors: Tezos core developers
 last_update:
-  date: 23 January 2024
+  date: 14 February 2024
 ---
 
 Our baker needs a user account consisting of a pair of keys and an address.
-The simplest way to get an account that works with Weeklynet is to use the Octez client to randomly generate them and associate them to the `my_baker` alias:
 
-```bash
-octez-client gen keys my_baker
-```
+1. Open a new terminal window in the same environment.
+If you are using a Docker container, you can enter the container with the `docker exec` command, as in `docker exec -it my-image /bin/sh`.
+To get the name of the Docker container, you run the `docker ps` command.
 
-The address of the generated account can be obtained with the following command:
+1. Create or import an account in the Octez client.
+The simplest way to get an account that works with Weeklynet is to use the Octez client to randomly generate an account.
+This command creates an account and associates it with the `my_baker` alias:
 
-```bash
-octez-client show address my_baker
-```
+   ```bash
+   octez-client gen keys my_baker
+   ```
 
-Let's record this address in a shell variable, this will be useful for the some commands which cannot get addresses by their octez-client aliases.
+   The address of the generated account can be obtained with the following command:
 
-```bash
-MY_BAKER="$(octez-client show address my_baker | head -n 1 | cut -d ' ' -f 2)"
-```
+   ```bash
+   octez-client show address my_baker
+   ```
 
-At this point, the balance of the `my_baker` account is still empty as can be seen with the following command:
+1. Record this address in a shell variable so you can use it for commands that cannot get addresses by their Octez client aliases:
 
-```bash
-octez-client get balance for my_baker
-```
+   ```bash
+   MY_BAKER="$(octez-client show address my_baker | head -n 1 | cut -d ' ' -f 2)"
+   ```
 
-In order to get some consensus and DAL rights, we need to put some tez in the account. Fortunately, getting free testnet tez is easy thanks to the testnet faucet. To use it, we need to enter the generated address in the Weeklynet faucet linked from https://teztnets.com/weeklynet-about. We need at least 6k tez for running a baker but the more tez we have the more rights we will get and the shorter we will have to wait to produce blocks and attestations. That being said, baking with too much stake prevents us from leaving the network without disturbing or even halting it so to avoid breaking the network for all other testers let's not be too greedy. 50k tez is enough to get enough rights to easily check if our baker behaves as expected while not disturbing the network too much when our baker stops operating.
+   At this point, the balance of the `my_baker` account is still zero, as you can see by running this command:
 
-We can verify that the faucet sent the tez to the account with the  same `get balance` command:
+   ```bash
+   octez-client get balance for my_baker
+   ```
 
-```bash
-octez-client get balance for my_baker
-```
+1. Get some tez from the Weeklynet faucet.
 
-At this point, the `my_baker` account owns enough stake to bake but has still no consensus or DAL rights because we haven't declared our intention to become a baker to the Tezos protocol. This can be achieved with the following command:
+   In order to get some consensus and DAL rights, we need to put some tez in the account. Fortunately, getting free testnet tez is easy thanks to the testnet faucet. To use it, we need to enter the generated address in the Weeklynet faucet linked from https://teztnets.com/weeklynet-about. We need at least 6k tez for running a baker but the more tez we have the more rights we will get and the shorter we will have to wait to produce blocks and attestations. That being said, baking with too much stake prevents us from leaving the network without disturbing or even halting it so to avoid breaking the network for all other testers let's not be too greedy. 50k tez is enough to get enough rights to easily check if our baker behaves as expected while not disturbing the network too much when our baker stops operating.
 
-```bash
-octez-client register key my_baker as delegate
-```
+1. Verify that the faucet sent the tez to the account with the same `get balance` command:
 
-Seven cycles later (about 1h40 on Weeklynet), our baker will start receiving rights. To see for instance its consensus attestation rights in the current cycle, we can use the following RPC call:
+   ```bash
+   octez-client get balance for my_baker
+   ```
 
-```bash
-octez-client rpc get /chains/main/blocks/head/helpers/attestation_rights\?delegate="$MY_BAKER"
-```
+   At this point, the `my_baker` account owns enough stake to bake but has still no consensus or DAL rights because we haven't declared our intention to become a baker to the Tezos protocol.
 
-To see the DAL attestation rights of all bakers, we can use the following RPC call:
+1. Register your account as a delegate by running the following command:
 
-```bash
-octez-client rpc get /chains/main/blocks/head/context/dal/shards
-```
+   ```bash
+   octez-client register key my_baker as delegate
+   ```
 
-This command returns an array of DAL attestation rights. The 2048 shards which are expected to be attested at this level are shared between active bakers proportionally to their stake. Each baker is assigned a slice of shard indices represented in the output of this command by a pair consisting of the first index and the length of the slice. So to check if some rights were assigned to us we can filter the array to our baker by running this command:
+1. Stake the tez, saving a small amount for transaction fees.
+For example, if your account has 50k tez, stake 49990 tez by running this command:
 
-```bash
-octez-client rpc get /chains/main/blocks/head/context/dal/shards | grep "$MY_BAKER"
-```
+   ```bash
+   octez-client stake 49990 for my_baker
+   ```
+
+   Seven cycles later (about 1h40 on Weeklynet), our baker will start receiving rights. To see for instance its consensus attestation rights in the current cycle, we can use the following RPC call:
+
+   ```bash
+   octez-client rpc get /chains/main/blocks/head/helpers/attestation_rights\?delegate="$MY_BAKER"
+   ```
+
+   When your baker has attestation rights, the previous command returns information about them, as in this example:
+
+   ```json
+   [ { "level": 9484,
+    "delegates":
+      [ { "delegate": "tz1Zs6zjxtLxmff51tK2AVgvm4PNmdNhLcHE",
+          "first_slot": 280, "attestation_power": 58,
+          "consensus_key": "tz1Zs6zjxtLxmff51tK2AVgvm4PNmdNhLcHE" } ] } ]
+   ```
+
+   To see the DAL attestation rights of all bakers, we can use the following RPC call:
+
+   ```bash
+   octez-client rpc get /chains/main/blocks/head/context/dal/shards
+   ```
+
+   This command returns an array of DAL attestation rights. The 2048 shards which are expected to be attested at this level are shared between active bakers proportionally to their stake. Each baker is assigned a slice of shard indices represented in the output of this command by a pair consisting of the first index and the length of the slice. So to check if some rights were assigned to us we can filter the array to our baker by running this command:
+
+   ```bash
+   octez-client rpc get /chains/main/blocks/head/context/dal/shards | grep "$MY_BAKER"
+   ```
 
 When attestation rights are assigned to your baker, continue to [Step 4: Run an Octez DAL node on Weeklynet](./run-dal-node.md).

docs/tutorials/join-dal-baker/run-dal-node.md

@@ -5,7 +5,9 @@ last_update:
   date: 23 January 2024
 ---
 
-Start the DAL node by running this command:
+The DAL node is responsible for temporarily storing data and providing it to bakers and Smart Rollups.
+
+To start the DAL node, open a new terminal window in the same environment and run this command:
 
 ```bash
 octez-dal-node run >> "$HOME/octez-dal-node.log" 2>&1