docs: rephrase the vale warnings that have a better wording

Words the alex and Microsoft styles flag where a plainer one reads as well:
disabled/special/invalid as a state, primitive, trap, hang, several, click,
first-person FAQ questions, hyphenated adverb pairs. Left as they are: Let's
Encrypt, quoted UI labels and phrases, the generated forge CLI reference, and
the middle-click gesture.

docs/integrations/forge.md

@@ -204,7 +204,7 @@ read directly without a delivery — same `mark_read` call, no wake.
 
 ### Activation gates (graceful no-ops)
 
-The poller starts disabled and stays that way for any of:
+The poller starts switched off and stays that way for any of:
 
 - `HIVE_FORGE_URL` not set or not parseable as a URL (a hand-run
   harness; hive-c0re sets it from `swarm.forge.domain` on every hive).
@@ -215,7 +215,7 @@ The poller starts disabled and stays that way for any of:
   best-effort enrichment fetches of server-provided subject URLs;
   both unlikely; treated as fatal-to-the-task only).
 
-Disabled = the spawned task returns immediately. All other failure
+Switched off = the spawned task returns immediately. All other failure
 modes (HTTP errors, parse errors, mark-read failures) are
 best-effort: logged at debug/warn and retried next tick.
 

docs/integrations/matrix.md

@@ -400,7 +400,7 @@ surprising behaviour:
 - **`services.hyperhive.swarm.matrix.gatewayHost != ""`** — same footgun as `forge.domain`:
   empty string renders `.<hive>`-shaped garbage in both nginx
   `server_name` (treated as wildcard catch-all, surprising) and
-  `/etc/hosts` (invalid entry). `null` is the right opt-out shape;
+  `/etc/hosts` (malformed entry). `null` is the right opt-out shape;
   a config assertion rejects empty string explicitly.
 SSO is unconditional, so the three below are requirements of running a
 homeserver at all rather than of a setting: