Design 47 and the glossary: the batch's record in the chain is the rollout (ADR 0408's review)

00-META/glossary.md

@@ -222,7 +222,7 @@ every other domain has something to run on. **Recorded by** the controller and t
   records (nodes, settings, declared config, predefined keys), after each change commits in its store and only
   when the value differs, with one event per write. The store stays the record; the self-check compares
   the two and raises `mirror-drifted` on any difference
-  (ADR 0289, ADR 0356). Builds, delivery plans with their rollouts, and assignments are no mirrors: they are
+  (ADR 0289, ADR 0356). Builds, rollouts and assignments are no mirrors: they are
   the chain, kept on the bus as their only source (ADR 0408). Shortened to *mirror* where the
   text is about the controller's records; the builder's *mirrored* `upstream` image (Change and delivery) is
   a different thing, a copy of an outside image in the artifact store.
@@ -477,7 +477,7 @@ planner, the rollout). **Downstream of** Module, Core, Health and repair and Dat
 - **rollout** — the controller's sending of one batch's builds across nodes, at most one trunk commit per
   repository, tier by tier, to every node that runs each module at once (ADR 0276, ADR 0360). Rollouts that share a
   repository, a module or a graph edge run one after another; others run side by side (ADR 0407). It names every
-  merge it answers, and its record is part of its delivery plan's key on the bus (ADR 0408). A primitive the delivering stage
+  merge it answers, and its record is one key of the bus's rollouts bucket, a link of the chain (ADR 0408). A primitive the delivering stage
   asks for, not an object anyone manages. A **tier** is one step of a rollout: a module, then the modules
   built against it. The controller's verb `plans` lists the rollouts. A module is rolled out by its `roll`
   policy.