docs: Updated docs

docs/vantage/ssh-keys.md

@@ -28,7 +28,7 @@ library. You may optionally upload the private half too, in which case it is
 stored **AES-256-GCM encrypted** under `KEY_ENCRYPTION_KEY`.
 
 The JSON representation of a key exposes only `has_private_key` and
-`has_passphrase` — never the material. Retrieving a stored private key is its
+`has_passphrase` never the material. Retrieving a stored private key is its
 own endpoint and its own audit event.
 
 :::tip Why store a private key at all
@@ -38,7 +38,7 @@ you are not using the console, do not upload private halves.
 
 ## Assigning
 
-Assign a key to one or more servers. Within one poll interval — 30 seconds — the
+Assign a key to one or more servers. Within one poll interval 30 seconds the
 agent picks up the change.
 
 ## Revoking
@@ -58,7 +58,7 @@ until it ends. Kill sessions on the machine if that matters.
 
 Each poll:
 
-1. `SyncKeys` returns the desired set of public keys for that server.
+1. The control plane returns the desired set of public keys for that server.
 2. The agent reads `/root/.ssh/authorized_keys` and computes fingerprints.
 3. **If the sets match, it writes nothing.** No disk churn on unchanged state,
    which is most polls.
@@ -77,5 +77,5 @@ it in Vantage.
 ## Recovering from a lockout
 
 If you have removed every key from a machine and cannot get in, you still have
-the console — provided a private key is stored — or out-of-band access from your
+the console provided a private key is stored or out-of-band access from your
 hosting provider. Vantage has no backdoor and does not keep a break-glass key.