From 687d2f7f81d6e34a45ed35c1a4ac639a32fd89d4 Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Wed, 5 Aug 2026 15:59:12 +0100
Subject: [PATCH] docs(telemetry): use snake_case tuning namespace in getobject
 aggregation note

develop renamed CamelCase namespaces to snake_case (#7933), so
Tuning::kHardMaxReplyNodes is now tuning::kHardMaxReplyNodes.
---
 OpenTelemetryPlan/09-data-collection-reference.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/OpenTelemetryPlan/09-data-collection-reference.md b/OpenTelemetryPlan/09-data-collection-reference.md
index 7fe5ebf1da..3447718567 100644
--- a/OpenTelemetryPlan/09-data-collection-reference.md
+++ b/OpenTelemetryPlan/09-data-collection-reference.md
@@ -713,7 +713,7 @@ attributable to a stage rather than merely observed.
 
 **Aggregation.** `getobject_lookup_us` times the fetch loop once per request, and
 `getobject_lookups_total` is added once per request carrying the batch hit and miss totals. The
-loop is bounded by `Tuning::kHardMaxReplyNodes` (12288), so timing or counting each iteration
+loop is bounded by `tuning::kHardMaxReplyNodes` (12288), so timing or counting each iteration
 would cost more than the lookups it measures. `getobject_request_objects` records the requested
 count, which is what the charge bands price on. `getobject_charge` records only the dynamic
 component returned by `computeGetObjectByHashFee()`; the admission-time base charge is a constant.