review suggestions

Author: s1gr1d

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

@@ -18,6 +18,21 @@ sidebar_order: 1
 
 </SdkOption>
 
+<PlatformCategorySection supported={["server", "serverless"]}>
+  <SdkOption name="orgId" type='`${number}` | number'>
+
+    The organization ID for your Sentry project.
+
+    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
+    you can provide the ID with this option. The organization ID is used for trace propagation and features like `strictTraceContinuation`.
+
+    <Alert level="info">
+      The organization ID is used for features like <PlatformLink to="/configuration/options#strictTraceContinuation">strict trace continuation</PlatformLink>.
+    </Alert>
+
+  </SdkOption>
+</PlatformCategorySection>
+
 <SdkOption name="debug" type='boolean' defaultValue='false'>
 
 Turns debug mode on or off. If debug is enabled SDK will attempt to print out useful debugging information about what the SDK is doing.
@@ -386,22 +401,12 @@ If you want to disable trace propagation, you can set this option to `[]`.
     If set to `true`, the SDK will only continue a trace if the organization ID of the incoming trace found in the
     `baggage` header matches the organization ID of the current Sentry client.
 
-    The client's organization ID is extracted from the DSN or can be set with the `orgId` option.
+    The client's organization ID is extracted from the DSN or can be set with the <PlatformLink to={'/configuration/options#orgId'}>`orgId` option</PlatformLink>.
 
     If the organization IDs do not match, the SDK will start a new trace instead of continuing the incoming one.
     This is useful to prevent traces of unknown third-party services from being continued in your application.
 
   </SdkOption>
-
-  <SdkOption name="orgId" type='`${number}` | number'>
-
-    The organization ID for your Sentry project.
-
-    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
-    you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.
-
-  </SdkOption>
-
 </PlatformCategorySection>
 
 <PlatformCategorySection supported={['browser']}>

platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx

@@ -76,11 +76,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}

platform-includes/distributed-tracing/how-to-use/javascript.node.mdx

@@ -67,11 +67,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}

platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx

@@ -66,11 +66,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}

platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx

@@ -105,11 +105,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}

platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx

@@ -99,11 +99,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}

platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx

@@ -76,11 +76,11 @@ If your app crashes while a user is uploading a photo, you can trace exactly whe
 _Available since SDK version 10_
 
 When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
-By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
 as it can lead to unwanted traces, increased billing, and skewed performance data.
 
-To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
-It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
+Otherwise, it starts a new trace.
 This is useful if your application is a public API or receives requests from services outside your organization.
 
 ```javascript {5}