Update develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx

Co-authored-by: Liza Mock <[email protected]>

Author: cleptric

develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx

@@ -111,7 +111,7 @@ SDKs in TwP mode must store trace data in a way that it can be attached to event
 The exact storage mechanism is up to the SDK implementation but it is recommended to use the same mechanism as for regular traces.
 Usually this means storing the data on the scope in a field called `propagationContext` as [recommended here](/sdk/telemetry/traces/distributed-tracing/).
 
-Related, the `propagationContext` should be populated with a random `traceId` and `spanId` if no incoming trace is present.
+On a related note, the `propagationContext` should be populated with a random `traceId` and `spanId` if no incoming trace is present.
 This—in combination with the `sentry-trace` header specification requiring a `spanId`—has an important implication on the Sentry product:
 A non-existing `spanId` will be propagated along with the trace and attached to events.
 While not ideal, we accept this limitation as the Sentry product can and should handle non-existing (parent) spans anyway.