diff --git a/docs/scheduler/observability.md b/docs/scheduler/observability.md
index 34471003..d4b7d66e 100644
--- a/docs/scheduler/observability.md
+++ b/docs/scheduler/observability.md
@@ -61,7 +61,7 @@ itself, so it could do all of the above _and_ use the token anywhere else. The
 collector removes the token and keeps the pipe. Agents are inside the trust
 boundary (`docs/trust-boundary/security.md`: capability = accepted risk), so an agent being
 able to _send_ is an accepted extension of that boundary — but it's not
-closed by this design, and nothing here should be read as closing it.
+closed by this design, and don't read anything here as closing it.
 
 **The `agent` label is self-reported, and the hive→swarm authentication below
 doesn't change that.** Treat it as a convenience for grouping dashboards, never
@@ -280,8 +280,9 @@ records them (every turn, always).
 
 ## Hive-scoped metrics (hive-c0re)
 
-Everything above is measured **per agent**, tagged with the hive it runs in.
-These three are measured per **hive**, and carry no `agent` label — so a hive
+hive-c0re measures everything above **per agent**, tagged with the hive it
+runs in. It measures these three per **hive** instead, and they carry no
+`agent` label — so a hive
 that hosts no agents still reports, and "this hive is quiet" is
 distinguishable from "this hive is gone." Select them with
 `{hive!="",agent=""}`.
@@ -348,7 +349,8 @@ hive-metric <name> <value> [--type counter|gauge] [--temporality delta|cumulativ
   `1` each time and the collector accumulates) or `cumulative` (this call
   reports the running total, which a stateless one-shot CLI can't track
   itself).
-- `--labels key=value` — extra per-data-point labels. May be repeated.
+- `--labels key=value` — extra per-data-point labels. Repeat the flag for
+  more than one.
   `hive-metric` inherits the resource labels (agent, hive, swarm, service.name)
   automatically from `OTEL_RESOURCE_ATTRIBUTES` — don't re-specify them.