Use established terms in setup guidance

docs/setup_p2p.md

@@ -47,7 +47,7 @@ On the working first device:
 1. Run `Self-hosted LiveSync: Copy settings as a new Setup URI` from the command palette.
 2. Enter a new Setup URI passphrase.
 
-    ![Masked passphrase for the additional-device P2P Setup URI](../images/p2p-setup/guide-p2p-setup-copy-setup-uri-passphrase.png)
+    ![Masked passphrase for the P2P Setup URI for another device](../images/p2p-setup/guide-p2p-setup-copy-setup-uri-passphrase.png)
 
 3. Copy the resulting URI.
 
@@ -61,7 +61,7 @@ Keep the first device online. Store the new URI and its passphrase separately.
 2. Open onboarding, select `I am adding a device to an existing synchronisation setup`, and choose the recommended Setup URI method.
 3. Enter the Setup URI generated by the first device and its passphrase.
 
-    ![First-device P2P Setup URI entered on the second device](../images/p2p-setup/guide-p2p-setup-second-setup-uri.png)
+    ![P2P Setup URI from the first device entered on the second device](../images/p2p-setup/guide-p2p-setup-second-setup-uri.png)
 
 4. Select `Restart and Fetch Data`.
 
@@ -73,7 +73,7 @@ Keep the first device online. Store the new URI and its passphrase separately.
 
     ![P2P local-file policy](../images/p2p-setup/guide-p2p-setup-local-file-policy.png)
 
-6. In `P2P Rebuild`, confirm that the expected first-device name is shown, then select `Sync`.
+6. In `P2P Rebuild`, confirm that the expected name of the first device is shown, then select `Sync`.
 
     ![Selecting the first device for P2P Rebuild](../images/p2p-setup/guide-p2p-setup-select-first-device.png)
 
@@ -83,16 +83,16 @@ Keep the first device online. Store the new URI and its passphrase separately.
 
 8. Keep both devices open until the test note appears on the second device.
 
-    ![First-device note received by the second P2P device](../images/p2p-setup/guide-p2p-setup-first-to-second.png)
+    ![Note from the first device received by the second P2P device](../images/p2p-setup/guide-p2p-setup-first-to-second.png)
 
 ## Verify the return journey
 
-Create a second ordinary note on the second device. Keep automatic announcements disabled and prove the next finite synchronisation explicitly:
+Create a second ordinary note on the second device. Keep automatic announcements disabled, then run and verify the next synchronisation explicitly:
 
 1. Open `P2P Status` on both devices.
 2. If a peer no longer appears, select `Disconnect` and then `Open connection` on the first device, followed by the second device. The device which joins last is advertised to devices which are already in the room.
 3. On the first device, select `Refresh`, verify the second-device name, then select `Replicate now`.
-4. On the second device, verify the requesting first-device name and select `Accept` or `Accept Temporarily`.
+4. On the second device, verify the name of the requesting first device and select `Accept` or `Accept Temporarily`.
 
     ![Explicit return-journey connection request on the second device](../images/p2p-setup/guide-p2p-setup-connection-request-2.png)
 
@@ -119,7 +119,7 @@ An announcement contains no Vault data and does not transfer a change by itself.
 - Check signalling relay reachability separately from WebRTC connectivity.
 - Review VPN and TURN options in [Peer-to-Peer Synchronisation Tips](./tips/p2p-sync-tips.md).
 
-## Controlled or self-hosted bootstrap
+## Controlled or self-hosted setup
 
 The ordinary route above starts in the plug-in UI and can use the project's public signalling relay. For a controlled deployment, prepare your own Nostr-compatible relay and enter it in `Signalling relay URLs` on every device.