docs: drop redundant hyphens from -ly adverb + adjective/participle compounds

Fixes 22 of 23 Microsoft.Hyphens hits: an adverb ending in -ly doesn't
need a hyphen to the word it modifies (minimally scoped, currently
running, deliberately stopped, ...) -- the -ly ending already
unambiguously signals it's modifying the following word, so the
hyphen is redundant per Microsoft style.

Left one hit alone: docs/web-ui/dashboard.md's 'checked-not-originally-
active' is a single 4-word compound designator (parallel structure
with 'unchecked-was-active' right before it in the same sentence,
describing a diffing algorithm's two possible states), not an
ordinary -ly-adverb modifier -- dropping just the one hyphen vale
flagged would have broken the compound into a dangling
'checked-not-originally active' fragment. Also rewrote
docs/scheduler/coordinator.md's 'still-fully-queued' as a predicate
('DAGs that are still fully queued') rather than leaving a similar
broken partial-hyphen chain, since 'still' and 'fully' are both plain
adverbs with no reason to hyphenate at all once dehyphenated
consistently.

Verified via vale: only the one deliberately-left hit remains.

docs/scheduler/coordinator.md

@@ -121,7 +121,7 @@ The `stop` / `start` power ops write the durable `wanted` intent via a head
 so intent-write + reconcile is atomic per-agent. `restart` is the exception:
 it writes _no_ intent (no `SetWanted` head) — it bounces the container and
 lets the tail `Reconcile` converge to the agent's existing `wanted`, so a
-deliberately-stopped agent isn't forced back up by a hive-wide restart. The
+deliberately stopped agent isn't forced back up by a hive-wide restart. The
 hive-wide power ops — `restart`, `stop`, and `start` — take an agent _list_:
 a hive-wide `hivectl restart` / `stop` / `start` is ONE DAG with a per-agent
 subgraph each (independent roots, run concurrently on their own leases), not
@@ -158,8 +158,8 @@ reparent(moves):   Reparent(moves)   (no rebuild — topology.json is read live)
 Notable collapses:
 
 - **`rebuild` is one uniform shape** — no `was_running` branch.
-  `StopForUpdate` noops when already down; the tail `Reconcile` autanoops the
-  start when `wanted = Offline` (a rebuild of a deliberately-stopped agent
+  `StopForUpdate` noops when already down; the tail `Reconcile` autonoops the
+  start when `wanted = Offline` (a rebuild of a deliberately stopped agent
   leaves it stopped).
 - **The swap-failure recovery-start is structural**: `Reconcile` deps on
   `Swap` with the one `AfterAny` edge in the system — it runs after `Swap`
@@ -264,7 +264,7 @@ Two consequences worth knowing:
   suppression across the build and tail, where a vanished container is still a
   real crash.
 
-Among simultaneously-ready nodes competing for a resource, DAG-submit order
+Among simultaneously ready nodes competing for a resource, DAG-submit order
 wins (FIFO) so bulk operations drain predictably. The scheduler also owns the
 DAG-lifetime transient guard (dashboard pill + crash-watch suppression),
 created on lease acquisition and dropped when the DAG settles terminal.
@@ -279,7 +279,7 @@ Submit-time dedup was removed with the agent-per-node move (a multi-agent DAG
 has no single agent to key a dedup on), so every submit enqueues a fresh DAG;
 whether any dedup needs reintroducing is tracked as a follow-up.
 
-Cancel only applies to still-fully-queued DAGs (an in-flight nix build isn't
+Cancel only applies to DAGs that are still fully queued (an in-flight nix build isn't
 interruptible) — each op is one DAG now, so there are no child DAGs to cascade to.
 Roll-up state: `Failed` if any node failed, else `Running` / `Queued` /
 `Cancelled` / `Done`. The snapshot retains the 50 most recent terminal