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/tools/forge.md

@@ -146,7 +146,7 @@ distinct output shape — pick by what you need:
 Rule of thumb: **`view` first** when you're about to act on a thread (it
 shows everything and clears the unread guard so your follow-up `comment`
 isn't rejected); the JSON verbs (`issue`/`pr`) when a script needs one
-field; `pr status` when the only question is "can I merge it."
+field; `pr status` when the only question is whether it can merge.
 
 ### Contributing to a read-only repo (`clone` + `pr create --agit`)
 

docs/tools/matrix.md

@@ -109,7 +109,7 @@ The summary depends on the room's unread state:
 
 - **One unread message**: `[matrix] <sender> in <room>: <body> —
   use read_room to view, mark_read to clear`
-- **Several unread messages**: `[matrix] N unread in <room> —
+- **Multiple unread messages**: `[matrix] N unread in <room> —
   use read_room to view, mark_read to clear`
 
 **Multi-account prefix**: when the daemon serves more than one account

docs/tools/subagent.md

@@ -200,7 +200,7 @@ renders it says so. Read the diff and the gate output regardless.
 parent that polls `status` sees the block without reading anything else.
 `continue` is how you answer it.
 
-## Is it working, or is it wedged?
+## Telling working from wedged
 
 `status` reporting **running** says the daemon tracks a process, which a
 wedged subagent satisfies as fully as a busy one. A running answer therefore
@@ -209,7 +209,7 @@ an age climbing into the minutes means it's stuck. That one number
 replaces inferring the same thing from `ps` output and CPU-time deltas.
 It resets at each turn's spawn, so on a goal run it describes the turn in
 flight rather than the run — which is what you want, since a run that's
-making progress spends several perfectly healthy minutes.
+making progress spends a few perfectly healthy minutes.
 
 Every line the subagent's `claude` process writes bumps the timestamp —
 stream-json events, plain stdout chatter and stderr alike — and what the
@@ -432,7 +432,7 @@ worktree switching.
 
 One rule worth knowing before editing any of this: **the daemon never
 emits an empty `--tools` value**, and asserts rather than doing so. Not
-because of what an empty value does — that's exactly the point. Our own
+because of what an empty value does — that's exactly the point. The hive's own
 measurement and the installed `claude --help` disagree about whether
 `--tools ""` means "no tools" or reads as the flag being absent, and the
 answer belongs to whichever claude release the system has installed