diff --git a/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md b/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md
index b5d43586..17c423eb 100644
--- a/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md
+++ b/docs/superpowers/specs/2026-09-08-deployment-scheduling-design.md
@@ -355,9 +355,11 @@ Administration is available through the `WorkflowApi` schedule methods,
 `workflow.schedules.*` RPC, and Python client. The API/transport operations
 are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`,
 `pause_schedule`, `resume_schedule`, `delete_schedule`, and paginated
-`list_schedule_occurrences`; the Python facade maps them to the names listed
-above. Creation validates the trigger, the deployment, the binding shapes, and
-a sample-occurrence
+`list_schedule_occurrences`; the Python facade names these operations
+`create_schedule`, `schedule`, `schedules`, `update_schedule`,
+`pause_schedule`, `resume_schedule`, `delete_schedule`, and
+`schedule_occurrences`. Creation validates the trigger, the deployment, the
+binding shapes, and a sample-occurrence
 resolution against the pinned root schema, and starts the consumed
 watermark at creation (no pre-creation backfill). Updates are
 revision-checked; pause/resume/delete mirror the poll-loop transitions;