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

Co-authored-by: Roman Zavarnitsyn <[email protected]>

Author: philipphofmann

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

@@ -28,7 +28,7 @@ The BatchProcessor MUST send all spans and logs to avoid data loss in the follow
 2. When the user calls  `SentrySDK.close()`, the BatchProcessor MUST send all data in memory.
 3. When the application shuts down gracefully, the BatchProcessor SHOULD send all data in memory. This is mostly relevant for mobile SDKs already subscribed to these hooks, such as [applicationWillTerminate](https://developer.apple.com/documentation/uikit/uiapplicationdelegate/applicationwillterminate(_:)) on iOS.
 4. When the application moves to the background, the BatchProcessor SHOULD send all data in memory and stop the timer. This is mostly relevant for mobile SDKs.
-5. If applicable to your environment, SDKs MUSt minimize data loss when sudden process terminations occur. Refer to the [Sudden Process Terminations](#sudden-process-terminations) section for more details.
+5. If applicable to your environment, SDKs MUST minimize data loss when sudden process terminations occur. Refer to the [Sudden Process Terminations](#sudden-process-terminations) section for more details.
 
 The detailed specification is written in the [Gherkin syntax](https://cucumber.io/docs/gherkin/reference/). The specification uses spans as an example, but the same applies to logs or any other future telemetry data.