From 67d51cc9ed415184eed61a2b5753972195eb85db Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Wed, 2 Sep 2026 20:31:45 +0100
Subject: [PATCH] docs(telemetry): ground the nodestore threshold rule without
 narrating the table

The rule's rationale said its three points were 'learned from a dataset that an
earlier version of this table got wrong'. That earlier table exists only in this
branch's intermediate commits, which a squash merge does not publish, so the
sentence points at nothing a reader can check.

The measured figures behind each point are unchanged.

Documentation only.
---
 docs/telemetry-runbook.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/telemetry-runbook.md b/docs/telemetry-runbook.md
index de7e1f5047..90f48b9f77 100644
--- a/docs/telemetry-runbook.md
+++ b/docs/telemetry-runbook.md
@@ -3182,7 +3182,7 @@ Then read the answer off the pair:
 | Expensive | Depth over ~1.2 | **Both paths queueing.** Rarer, and neither fix on its own will be enough. Treat the larger of the two costs as the lead.                                                                                                                                     |
 
 **Why the rule is shaped this way.** Three points about the thresholds, each
-learned from a dataset that an earlier version of this table got wrong:
+grounded in a measured dataset rather than a round number:
 
 - **Read cost is a relative judgement, so the band has a floor and a ceiling, not
   one cut.** A cold read on our box measured 31.8 µs mean; a cold read on the