docs: Self review of doc pages

docs/hq/cloud-instances.md

@@ -9,18 +9,19 @@ A cloud instance is a Vantage control plane we run for you, reachable at
 
 ## Creating one
 
-1. **Overview → New instance**.
-2. Choose a name and a slug.
-3. Create.
+1. On **Overview**, choose **Create a cloud instance**. Once you already have an
+   instance, the same page offers **Buy a plan** instead.
+2. Choose **Cloud**, then the plan you want.
+3. Give the instance a name and confirm.
 
 The instance is provisioned with you as its owner, and a Free licence is issued
-immediately. The owner user inside it gets your HQ password hash **copied**, not
-shared see [People and roles](./people-and-roles.md).
+immediately. Your Vantage HQ password gets you into it, though the two are kept
+in step rather than shared. See [People and roles](./people-and-roles.md).
 
 ### Slugs
 
-The slug becomes your hostname label, so it is lowercase, and some names are
-reserved. Pick something you can say on a phone call.
+Your instance's address comes from the name you choose, lowercased, with some
+names reserved. Pick something short that you can say on a phone call.
 
 :::warning One Free instance per account, per deployment
 Creating a second Free cloud instance is refused. If you want another, it needs
@@ -41,9 +42,9 @@ affect anyone signing in or any agent syncing.
 
 Each instance on Overview is one record. Closed, it is a row. Open, it shows:
 
-- **Licence contents** tier, server allowance, features, expiry.
-- **Members** who has access and with what instance role.
-- **Actions** grant access, change configuration, renew.
+- **Licence contents**: tier, server allowance, features and expiry.
+- **Members**: who has access, and with what role.
+- **Actions**: grant access, change configuration, renew.
 
 ## Members
 
@@ -53,14 +54,15 @@ Granting access writes a real user into the instance. Covered fully in
 ## Changing what it can do
 
 Server allowance and per-instance features (browser console, single sign-on) are
-part of the instance's **entitlement**. Changing it goes through billing see
+part of the instance's **entitlement**, the configuration your licence is cut
+from. Changing it goes through billing. See
 [Licensing and entitlements](./licensing-and-entitlements.md) and
 [Billing](./billing.md).
 
 ## Renaming
 
-The display name is free to change. The slug is the hostname and is not
-casually changed ask support if you need it.
+The display name is free to change. The slug is part of your hostname, so ask
+support if you need that changed.
 
 ## What happens if the licence lapses
 
@@ -73,6 +75,4 @@ runs to its grace-padded expiry and then lapses.
 
 ## Deleting
 
-Ask support. Deletion is performed by the control plane, not by HQ the control
-plane is the only service that knows which collections carry the instance ID,
-and duplicating that list into HQ would be a list that drifts.
+Ask support.