diff --git a/03-DESIGN/01-to-be/47-milestones/G-21-provider-and-revert-ask.md b/03-DESIGN/01-to-be/47-milestones/G-21-provider-and-revert-ask.md
index 35c05b53..367c3a0a 100644
--- a/03-DESIGN/01-to-be/47-milestones/G-21-provider-and-revert-ask.md
+++ b/03-DESIGN/01-to-be/47-milestones/G-21-provider-and-revert-ask.md
@@ -95,7 +95,7 @@ choice within the record it cites, tested against [the principles](../../../00-M
     fingerprint, the kept data, its form and the node's reason in its own words, and says "<module> keeps running
     its newer build until you answer. Started on the live data, the older build reads data written in the newer
     form." Two options, each of level acknowledge: `hold`, "Keep it held", does "the node keeps running the newer
-    build, and the revert waits"; `live`, "Start it on the live data", does "the node starts the older build on the
+    build, and the revert waits"; `live`, "Start on the live data", does "the node starts the older build on the
     live data as it is, with nothing restored". It expires after the assigner's `AskLasts`, `OnExpiry` "the module
     keeps running its newer build". The answer is read from the router's record of the ask (§700).
   - **Raises the condition**, through mesh-sdk's finding writer (§461), with the finding `revert-held` (scope