Use established terms in setup guidance

docs/quick_setup.md

@@ -50,13 +50,13 @@ Create an ordinary test note and allow it to upload before adding another device
 
 ## Create a Setup URI for another device
 
-Generate the additional-device Setup URI from the working first device. This captures the settings which that device is actually using, rather than asking another device to reuse the bootstrap URI produced during server provisioning.
+Generate a Setup URI for another device from the working first device. This captures the settings which that device is actually using, rather than asking another device to reuse the Setup URI produced during server provisioning.
 
 1. Open the Obsidian command palette on the first device.
 2. Run `Self-hosted LiveSync: Copy settings as a new Setup URI`.
 3. Enter a new passphrase which will protect this Setup URI, then select `OK`.
 
-   ![Masked passphrase for a new additional-device Setup URI](../images/quick-setup/guide-quick-setup-copy-setup-uri-passphrase.png)
+   ![Masked passphrase for a new Setup URI for another device](../images/quick-setup/guide-quick-setup-copy-setup-uri-passphrase.png)
 
 4. Copy the resulting Setup URI, then select `OK`.
 
@@ -75,7 +75,7 @@ Start with a new or separately backed-up Vault. Do not use a production Vault co
 5. Paste the new Setup URI generated by the first device, enter its Setup URI passphrase, and select `Test Settings and Continue`.
 6. Review `Setup Complete: Preparing to Fetch Synchronisation Data`, then select `Restart and Fetch Data`.
 
-   ![Additional-device Fetch confirmation](../images/quick-setup/guide-quick-setup-second-fetch.png)
+   ![Fetch confirmation on the additional device](../images/quick-setup/guide-quick-setup-second-fetch.png)
 
 7. For a new or empty Vault, select `Overwrite all with remote files`. For a Vault with local work, stop and choose the appropriate strategy from the [Fast Setup guide](./tips/fast-setup.md).
 
@@ -83,7 +83,7 @@ Start with a new or separately backed-up Vault. Do not use a production Vault co
 
 8. When asked how to handle extra local files, the conservative choice is `Keep local files even if not on remote`. Select the delete option only when the local Vault is disposable and an exact remote copy is intended.
 
-   ![Additional-device local file policy](../images/quick-setup/guide-quick-setup-local-file-policy.png)
+   ![Local file policy on the additional device](../images/quick-setup/guide-quick-setup-local-file-policy.png)
 
 9. Allow retrieval, file reflection, and any requested restart to finish. Keep Obsidian open until the LiveSync progress indicators have cleared.
 
@@ -114,7 +114,7 @@ Use this path when CouchDB is ready but a Setup URI is unavailable. It configure
 5. On `Choose a synchronisation remote`, select `CouchDB`, then select `Continue to CouchDB setup`.
 6. Enter the complete CouchDB URL, username, password, and database name.
    - Obsidian Mobile requires HTTPS. Plain HTTP is suitable only for a trusted local connection from a desktop device.
-   - Use credentials which are allowed to connect to the selected database and, for this first-device path, create it when it does not exist.
+   - Use credentials which are allowed to connect to the selected database and, when configuring the first device, create it if it does not exist.
 7. `Check server requirements` is optional. It sends the displayed credentials to the configured server through Obsidian's internal request API, and some checks require CouchDB administrator access. The initial check is read-only. If it offers a server change, review and confirm that individual change separately.
 8. Select `Create or connect to database and continue`. Onboarding requires this connection test to succeed.
 9. Review `Setup Complete: Preparing to Initialise Server`, then select `Restart and Initialise Server`.