diff --git a/OpenTelemetryPlan/Phase9_taskList.md b/OpenTelemetryPlan/Phase9_taskList.md
index f3b79d7af5..3a318afc61 100644
--- a/OpenTelemetryPlan/Phase9_taskList.md
+++ b/OpenTelemetryPlan/Phase9_taskList.md
@@ -314,14 +314,14 @@ These metrics serve multiple external consumer categories identified during rese
 - Provision Grafana alert rules (`docker/telemetry/grafana/provisioning/alerting/`):
   - 6 rules in 3 groups — consensus/ledger (`LedgerHistoryMismatch`, `LedgerCloseStalled`), validator (`ValidationsMissed`, `ValidationsNotChecked`), job queue (`JobQueueTxOverflow`, `JobQueueLatencyHigh`)
   - `xrpld-default` webhook contact point + flat notification policy; auto-loaded via the existing `provisioning/` mount (no docker-compose change)
-  - `docker/telemetry/ALERTING.md` operator runbook (per-alert meaning, tuning, receiver wiring)
+  - Alerting operator docs (per-alert meaning, tuning, receiver wiring) now live in the Alerting section of `docs/telemetry-runbook.md`
 
 **Key modified files**:
 
 - `OpenTelemetryPlan/09-data-collection-reference.md`
 - `docs/telemetry-runbook.md`
 - `docker/telemetry/grafana/provisioning/alerting/{rules,contactpoints,policies}.yaml` (new)
-- `docker/telemetry/ALERTING.md` (new)
+- `docs/telemetry-runbook.md` (Alerting section added)
 
 ---
 
diff --git a/docs/superpowers/specs/2026-07-06-phase9-alerting-design.md b/docs/superpowers/specs/2026-07-06-phase9-alerting-design.md
index 0f3cfb39fd..d9750eac93 100644
--- a/docs/superpowers/specs/2026-07-06-phase9-alerting-design.md
+++ b/docs/superpowers/specs/2026-07-06-phase9-alerting-design.md
@@ -39,8 +39,9 @@ New files under `docker/telemetry/grafana/provisioning/alerting/`:
 | `policies.yaml`      | Default notification policy: route all alerts → `xrpld-default`, grouped by `alertname` + `exported_instance`.      |
 | `rules.yaml`         | 6 alert rules across 3 groups (below).                                                                              |
 
-Plus `docker/telemetry/ALERTING.md` — operator runbook: what each alert means,
-likely causes, and how to point the contact point at a real receiver.
+Plus the Alerting section of `docs/telemetry-runbook.md` — operator runbook:
+what each alert means, likely causes, and how to point the contact point at a
+real receiver.
 
 ## Alert rules