fix(develop): Fix typos (#12545)

Author: sentrivana

develop-docs/sdk/telemetry/traces/distributed-tracing/index.mdx

@@ -2,22 +2,22 @@
 title: Distributed Tracing
 ---
 
-This document describes how a SDK should propagate information between different services to connect all telemetry (errors, profiles, replays, transaction, check-ins, ...) from those services into one trace.
+This document describes how an SDK should propagate information between different services to connect all telemetry (errors, profiles, replays, transaction, check-ins, ...) from those services into one trace.
 
 For an overview see [Distributed Tracing](https://docs.sentry.io/product/performance/distributed-tracing/) in the product docs.
 
 Sentry uses three containers to hold trace information [`sentry-trace`](/sdk/performance/#header-sentry-trace), [`traceparent`](/sdk/performance/#header-traceparent) and [`baggage`](/sdk/performance/dynamic-sampling-context/#baggage-header).
 
-With these containers you can propagate a trace to a down-stream service. By either
-- adding `sentry-trace`, `traceparent` and `baggage` HTTP headers (when doing outgoing HTTP requests),
+With these containers you can propagate a trace to a down-stream service by either:
+- adding `sentry-trace`, `traceparent` and `baggage` HTTP headers (when making outgoing HTTP requests),
 - adding `sentry-trace`, `traceparent` and `baggage` as meta data (when putting tasks into a queue, details are specific to the queue you want to support), or
 - setting environment variables (when calling another process). In this case the env variables should be called `SENTRY_TRACE`, `SENTRY_TRACEPARENT` and `SENTRY_BAGGAGE`.
 
 The SDK running in the receiving service needs to make sure to pick up incoming trace information by
 - reading `sentry-trace`, `traceparent` and `baggage` headers for each incoming HTTP request,
 - reading `sentry-trace`, `traceparent` and `baggage` meta data when retrieving an item from a queue, or
-- reading the environment variables `SENTRY_TRACE`, `SENTRY_TRACEPARENT` and `SENTRY_BAGGAGE` on start up.
+- reading the environment variables `SENTRY_TRACE`, `SENTRY_TRACEPARENT` and `SENTRY_BAGGAGE` on startup.
 
 In case both `sentry-trace` and `traceparent` are present, `sentry-trace` takes precedence.
 
-This trace information should be stored in the "propagation context" of the current scope. This makes sure that all telemetry that is emmited from the receiving service to Sentry will include the correct trace information.
+This trace information should be stored in the "propagation context" of the current scope. This makes sure that all telemetry that is emitted from the receiving service to Sentry will include the correct trace information.