docs: Updated docs

docsite/docs/operations/agent-updates.md

@@ -10,7 +10,6 @@ themselves on command.
 ## Checking the current version
 
 Each server's detail page shows the version it reported at its last sync.
-`GET /api/agent/latest-version` reports the newest release available.
 
 ## Updating from the UI
 
@@ -21,8 +20,6 @@ version. The agent then:
 2. Verifies the SHA-256 against `checksums.txt`.
 3. Stops itself, replaces the binary in place, and starts again.
 
-`Restart=always` on the systemd unit is what makes the last step work.
-
 The server briefly goes `offline` and comes back within a poll interval or two.
 
 ## Updating from the machine

docsite/docs/operations/backups.md

@@ -52,16 +52,9 @@ cp /opt/vantage/.env /secure-location/vantage.env
 
 Treat it as a credential in its own right it holds the encryption key.
 
-## Run logs
-
-Workflow run logs live in the `./data` bind mount, not in the database. They are
-swept on the retention schedule anyway, so most people do not back them up. If
-you keep them for compliance, set retention to `0` (forever) and include the
-directory.
-
 ## What a restore gives you
 
-Everything: fleet, keys, assignments, workflows and their history, monitors and
+Everything: server, keys, assignments, workflows and their history, monitors and
 incidents, secrets, settings and the audit log.
 
 What it does **not** do is reconcile the world. After a restore: