Update to new api

Author: Luca Forstner

docs/platforms/javascript/common/configuration/sampling.mdx

@@ -42,8 +42,8 @@ The Sentry SDKs have two configuration options to control the volume of transact
 
 2. Sampling function (<PlatformIdentifier name="traces-sampler" />) which:
    - Samples different transactions at different rates
-   - <PlatformLink to="/configuration/filtering/">Filters</PlatformLink> out some
-     transactions entirely
+   - <PlatformLink to="/configuration/filtering/">Filters</PlatformLink> out
+     some transactions entirely
    - Modifies default [precedence](#precedence) and [inheritance](#inheritance) behavior
 
 By default, none of these options are set, meaning no transactions will be sent to Sentry. You must set either one of the options to start sending transactions.
@@ -98,7 +98,6 @@ There are multiple ways for a transaction to end up with a sampling decision.
 
 When there's the potential for more than one of these to come into play, the following precedence rules apply:
 
-1. If a sampling decision is passed to <PlatformIdentifier name="start-transaction" />, that decision will be used, overriding everything else.
 1. If <PlatformIdentifier name="traces-sampler" /> is defined, its decision will be used. It can choose to keep or ignore any parent sampling decision, use the sampling context data to make its own decision, or choose a sample rate for the transaction. We advise against overriding the parent sampling decision because it will break distributed traces)
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined, but there's a parent sampling decision, the parent sampling decision will be used.
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined and there's no parent sampling decision, <PlatformIdentifier name="traces-sample-rate" /> will be used.

platform-includes/performance/traces-sampler-as-sampler/javascript.mdx

@@ -14,7 +14,7 @@ interface SamplingContext {
 Sentry.init({
   // ...
 
-  tracesSampler: ({ name, attributes, parentSampled }) => {
+  tracesSampler: ({ name, attributes, inheritOrSampleWith }) => {
     // Do not sample health checks ever
     if (name.includes("healthcheck")) {
       return 0;
@@ -30,24 +30,17 @@ Sentry.init({
       return 0.01;
     }
 
-    // Inherit the samle rate of the incoming trace if there is one. Sampling is deterministic
-    // for one entire trace, i.e. if the parent was sampled, we will be sampled too at the same
-    // rate.
-    if (typeof parentSampleRate === "number") {
-      return parentSampleRate;
-    }
-
-    // Else, use default sample rate
-    return 0.5;
+    // Otherwise, inherit the sample sampling decision of the incoming trace, or use a fallback sampling rate.
+    return inheritOrSampleWith(0.5);
   },
 });
 ```
 
 <Alert title="parentSampleRate">
 
-The `parentSampleRate` sampling context was introduced in version 9 of the SDK.
-To inherit sampling decisions in earlier versions of the SDK, us the `parentSampled` sampling context.
+The `inheritOrSampleWith` sampling context utility was introduced in version 9 of the SDK.
+To inherit sampling decisions in earlier versions of the SDK, use the `parentSampled` sampling context.
 
-Going forward, using `parentSampleRate` is strongly encouraged over using `parentSampled`, because it allows for deterministic sampling and metric extrapolation for downstream traces.
+Going forward, using `inheritOrSampleWith()` is strongly encouraged over using `parentSampled`, because it allows for deterministic sampling and metric extrapolation for downstream traces.
 
 </Alert>