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/agent-lifecycle/agent-roster.md

@@ -66,7 +66,7 @@ system-level facts live.
   degrades safely to "no agents" (covers a fresh install that hasn't
   synced yet).
 - **Reconcile** — runs alongside the periodic meta/flake regeneration.
-  Adds newly-spawned agents, drops removed ones. Reconcile keeps agents
+  Adds newly spawned agents, drops removed ones. Reconcile keeps agents
   whose config repo exists but that haven't spawned yet, so the gap until
   the container appears doesn't churn the file.
 
@@ -118,7 +118,7 @@ state dirs work as for every other agent.
   permissions alone, the same mechanism for every agent
   ([`docs/turn-loop/mcp.md`](../turn-loop/mcp.md)). Ruth's permissions
   are the default plus `manage_root_agent`, stored for her like any grant.
-- **State dirs** — _not_ special-cased: `HYPERHIVE_STATE_DIR` is
+- **State dirs** — _not_ treated as an exception: `HYPERHIVE_STATE_DIR` is
 injected uniformly via `systemd.globalEnvironment` for every
 container including the manager, so all token/state paths resolve
 through it the same way everywhere.

docs/agent-lifecycle/config-changes.md

@@ -68,7 +68,7 @@ target hive to deploy it.
 An agent created from an [archetype](../swarm/archetypes.md) gets no
 config repo: its hive builds it from the archetype's module.
 
-Changing what the template seeded isn't a special case: like every
+Changing what the template seeded isn't an exception: like every
 later change, it's a PR on that config repo, made from a clone and
 merged by an operator on the forge (see [Config changes](#config-changes)).
 
@@ -376,7 +376,7 @@ Differences from sub-agents:
   authoritative applied repo (see "Root-agent view of applied" below).
 - Its socket comes from the generic per-agent registration, in the same
   per-agent runtime dir as any other agent (`/run/hyperhive/agents/ruth/`),
-  not a special manager-only path.
+  not a separate manager-only path.
 
 **Migration note** (for older hosts): drop any `containers.root =
 { ... }` block from your host NixOS config, and any `services.hyperhive.ruthless`
@@ -406,7 +406,7 @@ and nothing in the tree constructs it; this removal dropped the push path
 genuinely needs to interrupt an agent's turn loop, not because
 anything live uses it today.
 
-**A previously-running container crashing** used to be exactly that
+**A previously running container crashing** used to be exactly that
 case (`ContainerCrash`, routed to the root agent via
 `Coordinator::notify_manager`) — it no longer drives any agent turn at
 all. `crash_watch` now only `tracing::warn!`s `"container crash

docs/agent-lifecycle/persistence.md

@@ -4,7 +4,7 @@ Where state lives, what survives what, and how it's bounded.
 
 ## For operators
 
-The short answer to "will I lose anything": **destroying an agent
+The short answer to "does anything disappear": **destroying an agent
 keeps its state, purging it doesn't.**
 
 - **`DESTR0Y`** (the default action) stops and removes the container