fix typos

Author: jaffrepaul

develop-docs/sdk/telemetry/spans/span-api.mdx

@@ -7,7 +7,7 @@ title: Span API
 </Alert>
 
 <Alert level="info">
-  The APIs specified in this documents MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation.
+  The APIs specified in this document MUST be implemented by all SDKs that don't use OpenTelemetry as their underlying tracing implementation.
   SDKs using OTel SHOULD follow their own already established span APIs but MAY orient themselves on this document if applicable.
 </Alert>
 
@@ -19,7 +19,7 @@ This span has no parent span and groups together its children with a representat
 The topmost span within a service boundary is called the "Segment Span". 
 Segment spans have a `parent_span_id` pointing to a "remote" span from the parent service. 
 
-For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frotnend.
+For example, a distributed trace from backend to frontend, would have a segment span for the backend, and a segment span for the frontend.
 The frontend segment span is also the root span of the entire span tree. 
 
 SDKs MUST NOT expose names like "segment span" (e.g. in APIs) to users and SHOULD NOT (read "avoid") exposing "root span" if possible.
@@ -52,7 +52,7 @@ interface Span {
 When implementing the span interface, consider the following guidelines:
 
 - SDKs MAY implement additional APIs, such as getters/setters for properties (e.g. `span.getStatus()`), or additional methods for convenience (e.g. `Span::spanContext()`). 
-- SDK implementers SHOULD dissalow direct mutation (without setters) of span properties such as the span name, depending on the plaform and the challenges involved.
+- SDK implementers SHOULD disallow direct mutation (without setters) of span properties such as the span name, depending on the platform and the challenges involved.
 - SDK implementers MAY disallow direct read access to span properties, depending on the platform and the challenges involved.
 
 ## Span Starting APIs