docs: Updated docs

docs/hq/accounts-and-signup.md

@@ -12,17 +12,17 @@ behind your instances: your team, your instances, their licences and billing.
 One account holds many people and many instances. Everyone in it has an account
 role:
 
-| Role | Can |
-| --- | --- |
-| `owner` | Everything, including billing |
-| `admin` | Invite people, create instances, grant instance access |
-| `member` | Read what the account holds |
+| Role     | Can                                                    |
+| -------- | ------------------------------------------------------ |
+| `owner`  | Everything, including billing                          |
+| `admin`  | Invite people, create instances, grant instance access |
+| `member` | Read what the account holds                            |
 
 Reading is open to any signed-in member. Every mutation except changing your own
 password requires `owner` or `admin`. Billing is owner-only.
 
-The three words are the same as the control plane's roles, on purpose — but they
-are separate things. Your account role governs the portal; your role *inside* an
+The three words are the same as the control plane's roles, on purpose but they
+are separate things. Your account role governs the portal; your role _inside_ an
 instance governs that instance.
 
 ## Signing up
@@ -37,7 +37,7 @@ you later create or link one.
 
 :::info Verify before you can sign in
 An unverified account gets a distinct "check your email" message rather than a
-generic authentication failure — the address is already known to be yours, so
+generic authentication failure the address is already known to be yours, so
 there is nothing to protect by being vague.
 :::
 
@@ -45,7 +45,7 @@ Verification links are valid for **24 hours**. The token is 32 random bytes and
 only its SHA-256 hash is stored, so a leaked database yields no working links.
 
 If the verification email cannot be sent, the signup is rolled back rather than
-left stranded — retry rather than assuming a half-created account is in the way.
+left stranded retry rather than assuming a half-created account is in the way.
 
 ## Signing in
 
@@ -54,11 +54,11 @@ signing in to HQ does not sign you in to an instance, and vice versa.
 
 ## What comes next
 
-| You want | Go to |
-| --- | --- |
-| A Vantage instance we run | [Cloud instances](./cloud-instances.md) |
-| To license an install you run | [Self-hosted instances](./self-hosted-instances.md) |
-| To add colleagues | [People and roles](./people-and-roles.md) |
+| You want                       | Go to                                                         |
+| ------------------------------ | ------------------------------------------------------------- |
+| A Vantage instance we run      | [Cloud instances](./cloud-instances.md)                       |
+| To license an install you run  | [Self-hosted instances](./self-hosted-instances.md)           |
+| To add colleagues              | [People and roles](./people-and-roles.md)                     |
 | To understand tiers and limits | [Licensing and entitlements](./licensing-and-entitlements.md) |
 
 ## The portal layout