From da5494fb74cd800af661a9cabc87b1b5ce16c56c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Stefan=20P=C3=B6lz?=
 <38893694+Flash0ver@users.noreply.github.com>
Date: Mon, 26 Jan 2026 15:24:27 +0100
Subject: [PATCH] docs(client-reports): fix `reason` inconsistency

Clarify handling of HTTP status codes for client reports.
---
 develop-docs/sdk/telemetry/client-reports.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/develop-docs/sdk/telemetry/client-reports.mdx b/develop-docs/sdk/telemetry/client-reports.mdx
index 1a812da604d59..368cb36df07bc 100644
--- a/develop-docs/sdk/telemetry/client-reports.mdx
+++ b/develop-docs/sdk/telemetry/client-reports.mdx
@@ -165,7 +165,7 @@ an envelope item, for example, with the response 429, the client SDK must not re
 this as the server already does. Still, the SDK must record lost envelope items
 when dropping them itself, for example, caused by an active rate limit. SDKs can put
 a simple optional check for HTTP status codes in place where any code `>= 400` except
-`429` will be recorded as `network_error`. The client SDKs can assume that client
+`429` will be recorded as `send_error`. The client SDKs can assume that client
 reports never get rate limited. The server is minimizing the possibility of client
 reports getting rate limited, but the SDKs shouldn't worry about this edge case as
 this feature is best-effort.