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

@@ -125,8 +125,8 @@ Note that in the case of using the non-recording span, the span is also not samp
 
 ## Historical Context
 
-TwP mode was introduced after SDKs were already capable of sending spans and transactions. Before TwP, SDKs would only handle traces if span sending was enabled and otherwise not attach trace data to any events.
-The primary motivation for TwP was to ensure that errors across application or service boundaries are still connected if they occurred in the same trace.
+TwP mode was introduced after SDKs were already capable of sending spans and transactions. Before TwP, SDKs would only handle traces if span-sending was enabled. Otherwise, no trace data would be attached to any events.
+The primary motivation for TwP was to ensure that errors across application or service boundaries were still connected if they occurred in the same trace.
 
 The name "Tracing without Performance" was chosen because at the time of introduction, we associated spans purely with performance monitoring.
 Today, we associate spans with "Tracing" in general, and only (some of) the data from spans with Performance Monitoring.