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

@@ -107,8 +107,8 @@ Traces in TwP mode should have the same duration as regular traces.
 For example, a TwP trace for a backend server should generally last for the duration of one individual request.
 This usually corresponds with the lifetime of an isolation scope (or current scope created within the isolation scope).
 
-SDKs in TwP mode must store trace data in a way that it can be attached to events and propagated to outgoing requests.
-The exact storage mechanism is up to the SDK implementation but it is recommended to use the same mechanism as for regular traces.
+SDKs in TwP mode must store trace data in a way that makes it possible for them to be attached to events and propagated to outgoing requests.
+The exact storage mechanism is up to the SDK implementation, but we recommended using 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/).
 
 On a related note, the `propagationContext` should be populated with a random `traceId` and `spanId` if no incoming trace is present.