Apply suggestions from code review

Co-authored-by: Anton Pirker <[email protected]>

Author: cleptric

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

@@ -74,7 +74,7 @@ This Option replaces the non-standardized `tracingOrigins` option which was prev
 
 ### `strictTracePropagation`
 
-This option disables trace continuation from unknown 3rd party services that happen to be instrumented by a Sentry SDK.
+This should be a boolean value. Default is `false`. This option controls trace continuation from unknown 3rd party services that happen to be instrumented by a Sentry SDK.
 
 If the SDK can parse an org ID from the configured DSN, it must be propagated as a baggage entry with the key `sentry-org`. Given a DSN of `https://[email protected]/1`, the org ID is `1`, based on `o1`.
 
@@ -216,7 +216,7 @@ Without a `tracesSampler` callback, an SDK fully inherits sampling decisions for
 
 The random value is set according to the following rules:
 
-1. When an SDK starts a new trace, `sample_rand` is always set to a truly random number in range `[0, 1]`. This explicitly includes traces that are not sampled, as well as when the `tracesSampleRate` is set to `0.0` or `1.0`.
+1. When an SDK starts a new trace, `sample_rand` is always set to a random number in range `[0, 1]`. This explicitly includes traces that are not sampled, as well as when the `tracesSampleRate` is set to `0.0` or `1.0`.
 2. It is _recommended_ to generate the random number deterministically using the trace ID as seed or source of randomness. The exact method by which the random number is created is implementation defined and may vary between SDK implementations.
 3. On incoming traces, an SDK assumes the `sample_rand` value along with the rest of the DSC, overriding an existing value if needed.
 4. If `sample_rand` is missing on an incoming trace, the SDK creates and from now on propagates a new random number on-the-fly, based on the following rules: