diff --git a/docs/scheduler/coordinator.md b/docs/scheduler/coordinator.md
index 7cdd44d8..5d59515a 100644
--- a/docs/scheduler/coordinator.md
+++ b/docs/scheduler/coordinator.md
@@ -450,7 +450,7 @@ own. Its `DeployApply` node doesn't build: it merges, opens the two-phase
 meta deploy, and returns the chain above as a subgraph the scheduler grafts
 into the live DAG under that node. A `FinalizeDeploy` node gated on the
 graft's completion then plants the deploy tag — so `Reconcile`'s success
-answers "did the agent come back up?", the same way it does for every
+answers "did the agent come back up?" the same way it does for every
 other rebuild, instead of a fused inline start.
 
 The grafted nodes land _inside_ `DeployWindow`'s subtree, so they re-enter