docs: move node 1 onto the pinned tags once node 2 is in the pools, and check health after the failover test

src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx

@@ -357,7 +357,7 @@ Node 2 runs the same three files as node 1, with no installer and no database of
    NETBIRD_DASHBOARD_TAG=v2.93.0
    ```
 
-   Node 1 keeps running: these tags name the images it already runs.
+   Node 1 keeps running: these tags name the images it already runs. It switches to them in item 4.
 
 2. On node 2, create the same directory and copy three files into it from node 1: `config.yaml`, `.env` and `docker-compose.yml`. Two of them hold secrets, so copy them over an encrypted channel, such as `scp` or your configuration management tool's secret store, and keep them readable by root only:
 
@@ -372,7 +372,7 @@ Node 2 runs the same three files as node 1, with no installer and no database of
    docker compose logs netbird-server | grep -E 'Starting CloudServer|redis cache|Connected to NATS|license validated'
    ```
 
-4. Add node 2 to the load balancer's backend pools.
+4. Add node 2 to the load balancer's backend pools. Then run `docker compose up -d` on node 1, so that its containers also run under the pinned tags. Node 2 carries the traffic while node 1 restarts.
 
 To add more nodes later, repeat this step. Every node must have an identical `config.yaml`. Compare them with `sha256sum config.yaml`.
 
@@ -380,7 +380,7 @@ To add more nodes later, repeat this step. Every node must have an identical `co
 
 1. Log in to the dashboard at `https://app.example.com` and confirm your peers are connected.
 2. Make a change that no one depends on, and confirm peers pick it up. For example, rename a test peer on the dashboard's **Peers** page, and check that another peer that can reach it lists the new name in `netbird status -d` within seconds. Then rename it back.
-3. Stop the server on node 1 (`docker compose stop netbird-server dashboard`). The dashboard keeps working, and peers connected through node 1 reconnect through node 2 within seconds. Then start it again (`docker compose start netbird-server dashboard`).
+3. Stop the server on node 1 (`docker compose stop netbird-server dashboard`). The dashboard keeps working, and peers connected through node 1 reconnect through node 2 within seconds. Then start it again (`docker compose start netbird-server dashboard`), and confirm the load balancer's health checks report node 1 as healthy again.
 
 For more failure tests and day-to-day operations, see the [High Availability guide](/selfhosted/maintenance/scaling/high-availability).