diff --git a/docs/web-ui.md b/docs/web-ui.md
index 397122fc..f225677e 100644
--- a/docs/web-ui.md
+++ b/docs/web-ui.md
@@ -292,12 +292,12 @@ state + applied dirs; `POST /purge-tombstone/{name}`).
 
 Anything that fires at a future time. Operator-set schedules
 are created inline in the table (last row); agent self-paced
-reminders surface at the bottom as a sibling list (#460 —
-they share enough conceptual ground to live together).
+reminders surface at the bottom as a sibling list — they
+share enough conceptual ground to live together.
 
 **N3W SCH3DUL3 / QU3U3D SCH3DUL3S** — operator-managed
-scheduled prompts (#444 / #459). **Single-table layout**
-(#535): each schedule is one `<tr>`; columns are
+scheduled prompts. **Single-table layout**: each schedule is
+one `<tr>`; columns are
 `# | src | next | every | owner | body | …agents… | actions`.
 Agent columns are dynamic — `operator` + `manager` + every
 live container + any extra name that appears as a target on
@@ -308,26 +308,24 @@ headers tilt -45° via CSS so each column reads as a narrow
 ~28px strip; per-agent cells render as:
 
 - **active target** → `<button>✓</button>` that cancels just
-  that one target on click (replaces the per-row ✕ from the
-  pre-#535 targets sub-table)
+  that one target on click
 - **cancelled target** → muted `✕` glyph (no button —
   re-adding goes through the edit form's targets multi-select)
 - **not a target** → empty cell
 
 Per-schedule action column: a `↯ fire now` button sends an
-out-of-band manual pulse to every active target (#467 —
-recurring schedules keep their cadence; one-shots are
-consumed after the manual fire), an `✎ edit` button expands
-an inline edit form as a colspan'd row directly under the
-schedule's row (#474 — body / description / interval /
-next-fire / targets all editable; targets are a multi-select
-diff'd against the original active set so unchecked-was-
-active = `targets_remove`, checked-not-originally-active =
-`targets_add`; submit PATCHes `/api/schedules/{id}`), and a
-`✕` button cancels the whole schedule
-(`POST /api/schedules/{id}/cancel`).
+out-of-band manual pulse to every active target (recurring
+schedules keep their cadence; one-shots are consumed after
+the manual fire), an `✎ edit` button expands an inline edit
+form as a colspan'd row directly under the schedule's row
+(body / description / interval / next-fire / targets all
+editable; targets are a multi-select diff'd against the
+original active set so unchecked-was-active = `targets_remove`,
+checked-not-originally-active = `targets_add`; submit PATCHes
+`/api/schedules/{id}`), and a `✕` button cancels the whole
+schedule (`POST /api/schedules/{id}/cancel`).
 
-The table's last row is a permanent inline creation row (#564):
+The table's last row is a permanent inline creation row:
 inputs live directly in table cells (targets as checkboxes,
 body textarea that expands on focus, datetime-local pre-filled
 to 5 minutes from now, mini d/h/m/s number inputs (blank or
@@ -347,7 +345,7 @@ button hard-deletes (`POST /cancel-reminder/{id}`) and a
 `R3TRY` button re-arms one whose delivery failed
 (`POST /retry-reminder/{id}`). Backed by `GET /api/reminders`.
 Lives in the SCH3DUL3S tab alongside operator schedules so the
-operator has one place for everything time-fired (#460).
+operator has one place for everything time-fired.
 
 ### M4TR1X page (`/matrix/`, optional)