Update develop-docs/sdk/telemetry/spans/implementation.mdx

Author: Lms24

develop-docs/sdk/telemetry/spans/implementation.mdx

@@ -21,7 +21,7 @@ If you're implementing Span-First (as a PoC) in your SDK, take an iterative appr
 
 1. Add the Span v2 Envelope (type), serialization logic and any utilities necessary to support sending a new envelope. See [Span Protocol](../span-protocol) for more details.
 2. Add the top-level `traceLifecycle` (or `trace_lifecycle`) SDK init option which controls if traces should be sent as transactions or as spans (v2).
-   - The allowed values for this option MUST be `'static'` and `'strea'`.
+   - The allowed values for this option MUST be `'static'` and `'stream'`.
    - By default, the SDK MUST send traces as transactions (`'static'`). Span-First MUST be an opt-in feature.
    - Continue with adding Span-First logic which MUST only be applied if `traceLifecycle` is set to `'stream'`.
 3. As an initial PoC, leave your current transaction APIs in place and convert the transaction event to a v2 spans array to be sent in the new envelope.