fix more broken links

Author: Lms24

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

@@ -13,7 +13,7 @@ sidebar_order: 10
   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>
 
-This document provides guidelines for implementing Span-First in SDKs. This is purposefully NOT a full specification. For exact specifications, refer to the other pages under [Spans](./../index).
+This document provides guidelines for implementing Span-First in SDKs. This is purposefully NOT a full specification. For exact specifications, refer to the other pages under [Spans](..).
 
 ## How To Approach Span-First in SDKs
 
@@ -33,9 +33,9 @@ If you're implementing Span-First (as a PoC) in your SDK, take an iterative appr
    - TBD: Some SDKs already have `startSpan` or similar APIs. The migration path is still TBD but a decision can be made at a later stage.
 5. Implement the `captureSpan` [single-span processing pipeline](#single-span-processing-pipeline)
    - Either reuse existing heuristics (e.g. flush when segment span ends) or build a simple span buffer to flush spans (e.g. similar to the existing buffers for logs or metrics).
-   - Implementing the more complex [Telemetry Buffer](./../telemetry-buffer/index) can happen at a later stage.
+   - Implementing the more complex [Telemetry Buffer](./../../telemetry-buffer) can happen at a later stage.
 6. Achieve data parity with the existing transaction events.
-   - Ensure that the data added by integrations, event processors, etc to transaction events is also added to the spans (See [Event Processors](#event-processors)).
+   - Ensure that the data added by integrations, event processors, etc to transaction events is also added to the spans (See [Event Processors](#tbd-event-processors)).
    - Most additional data MUST only be added to the segment span. See [Common Attributes](../span-protocol/#common-attribute-keys) for attributes that MUST be added to every span.
    - Mental model: All data our SDKs _automatically_ add to a transaction, MUST also be added to the segment span.
 7. Implement the span telemetry buffer for proper, weighted span flushing. See [Span Buffer](#span-buffer) for more details.
@@ -109,7 +109,7 @@ SDK authors working on Span-First are encouraged to evaluate both options, try t
 
 ## Span Buffer
 
-This section is intentionally short because all buffering specification is being added to the [Telemetry Buffer](../../telemetry-buffer)page.
+This section is intentionally short because all buffering specification is being added to the [Telemetry Buffer](../../telemetry-buffer) page.
 
 Some rough pointers:
 - Given that SDKs SHOULD materialize and freeze the DSC as late as possible, the span buffer SHOULD enqueue span instances and at _flush time_ serialize them to JSON.