final touches

Author: philipphofmann

develop-docs/sdk/telemetry/spans/batch-processor.mdx

@@ -10,11 +10,11 @@ title: Batch Processor
   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 BatchProcessor batches spans and logs into one envelope to reduce the number of HTTP requests. When an SDK implements span streaming or logs, it MUST use a BatchProcessor, which is similar to [OpenTelemetry's Batch Processors](https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/README.md). The BatchProcessor holds finished spans and logs in memory and batches them together in envelopes. It uses a combination of time and size-based batching. When writing this, the BatchProcessor only handles spans and logs, but the SDK MAY use it for other telemetry data in the future.
+The BatchProcessor batches spans and logs into one envelope to reduce the number of HTTP requests. When an SDK implements span streaming or logs, it MUST use a BatchProcessor, which is similar to [OpenTelemetry's Batch Processor](https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/README.md). The BatchProcessor holds logs and finished spans in memory and batches them together into envelopes. It uses a combination of time and size-based batching. When writing this, the BatchProcessor only handles spans and logs, but an SDK MAY use it for other telemetry data in the future.
 
 ## Specification
 
-Whenever the SDK finishes a span or captures a log, it MUST put these into the BatchProcessor. The SDK MUST NOT put unfinished spans into the BatchProcessor.
+Whenever the SDK finishes a span or captures a log, it MUST put it into the BatchProcessor. The SDK MUST NOT put unfinished spans into the BatchProcessor.
 
 The BatchProcessor MUST start a timeout of 5 seconds when the SDK adds the first span or log. When the timeout exceeds, the BatchProcessor MUST send all spans or logs, no matter how many items it contains. The SDK MAY choose a different value for the timeout, but it MUST NOT exceed 30 seconds, as this can lead to problems with the span buffer on the backend, which uses a time interval of 60 seconds for determining segments for spans.
 
@@ -41,16 +41,16 @@ Scenario: Span added before timeout exceeds
     And doesn't reset the timeout
     And doesn't send the spans A and B in the BatchProcessor to Sentry
 
-Scenario: Spans with size of MiB - 1 byte added, timeout exceeds
-    Given spans with size of MiB - 1 byte in the BatchProcessor
+Scenario: Spans with size of 1 MiB - 1 byte added, timeout exceeds
+    Given spans with size of 1 MiB - 1 byte in the BatchProcessor
     When the timeout exceeds
     Then the SDK adds all the spans to one envelope
     And sends them to Sentry
     And resets the timeout
     And clears the BatchProcessor
 
-Scenario: Spans with size of MiB - 1 byte added within 4.9 seconds
-    Given spans with size of MiB - 1 byte in the BatchProcessor
+Scenario: Spans with size of 1 MiB - 1 byte added within 4.9 seconds
+    Given spans with size of 1 MiB - 1 byte in the BatchProcessor
     When the SDK finishes another span and puts it into the BatchProcessor
     Then the BatchProcessor puts all spans into one envelope
     And sends the envelope to Sentry