Update develop-docs/sdk/telemetry/telemetry-processor/index.mdx

Co-authored-by: isaacs <i@izs.me>

Author: philipphofmann

develop-docs/sdk/telemetry/telemetry-processor/index.mdx

@@ -12,7 +12,7 @@ sidebar_order: 5
   This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.
 </Alert>
 
-The telemetry processor ensures data is delivered efficiently to Sentry. It receives data from the client and forwards it to the transport. Its key responsibilities include buffering, rate limiting, client reporting, priority-based sending, and, on some platforms, offline caching. We recommend adding the telemetry processor only for high-volume data, such as spans, logs, and metrics. If your SDK doesn't implement any of these high-volume data features, it **MAY NOT** have a telemetry processor.
+The telemetry processor ensures data is delivered efficiently to Sentry. It receives data from the client and forwards it to the transport. Its key responsibilities include buffering, rate limiting, client reporting, priority-based sending, and, on some platforms, offline caching. We recommend adding the telemetry processor only for high-volume data, such as spans, logs, and metrics. If your SDK doesn't implement any of these high-volume data features, it **MAY** not have a telemetry processor.
 
 
 ```mermaid