Name fix time and fix budget in the glossary (issue 403, ADR 0313)

ADR 0313 makes the span from the move to fixing to delivered the operator's
target; the delivery budget stays a measure inside it, and its leaf figure is
three minutes since ADR 0304.

00-META/glossary.md

@@ -387,8 +387,14 @@ planner, the walk). **Downstream of** Module, Core, Health and repair and Data.
   Not a *core component* (ADR 0236's controller, node-engine, tool runner and bus, each with a health probe):
   the core modules add mesh-delivery and the resolver.
 - **delivery time** — from a delivery's merge to every node of its deploy plan that is heard from running its
-  modules' builds and reporting them healthy. Its **delivery budget** is what it is held to: five minutes for
+  modules' builds and reporting them healthy. Its **delivery budget** is what it is held to: three minutes for
-  a leaf module, ten for a core module (ADR 0282). Not the walk's time, which ends at the send.
+  a leaf module (ADR 0304), ten for a core module (ADR 0282). Not the walk's time, which ends at the send. A
+  measure inside the fix budget, not the operator's target (ADR 0313).
+- **fix time** — from an issue's first move to `fixing` to the moment the last of its fixes is delivered: the
+  operator's measure of a fix, the agent's work, the review and the checks included, the delivery time its last
+  part. Its **fix budget** is what it is held to: five minutes for a leaf module, ten for a core module, counted
+  from the move to `fixing`; an issue whose fixes move no module has none (ADR 0313). Not the delivery time,
+  which starts at the merge.
 - **release** — a person's word that a held delivery goes on; the verb `mesh-delivery.release`. Used in
   this sense only.
 - **rollback** — putting a node back on the build it ran before, by something other than the build being