some adjustments

Author: mydea

docs/platforms/javascript/common/tracing/trace-propagation/index.mdx

@@ -10,9 +10,7 @@ If the overall application landscape that you want to observe with Sentry consis
 
 ## What is Distributed Tracing?
 
-In the context of tracing events across a distributed system, distributed tracing acts as a powerful debugging tool. Imagine your application as a vast network of interconnected parts. For example, your system might be spread across different servers or your application might split into different backend and frontend services, each potentially having their own technology stack.
-
-When an error or performance issue occurs, it can be challenging to pinpoint the root cause due to the complexity of such a system. Distributed tracing helps you follow the path of an event as it travels through this intricate web, recording every step it takes. By examining these traces, you can reconstruct the sequence of events leading up to the event of interest, identify the specific components involved, and understand their interactions. This detailed visibility enables you to diagnose and resolve issues more effectively, ultimately improving the reliability and performance of your distributed system.
+<PlatformContent includePath="distributed-tracing/explanation" />
 
 ## Basic Example
 

platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx

@@ -1,27 +1,17 @@
-
 Distributed tracing will be set up automatically if you've <PlatformLink to="/tracing/">set up tracing</PlatformLink>.
 
+<Expandable title="What is Distributed Tracing?">
+  <PlatformContent includePath="distributed-tracing/explanation" />
+</Expandable>
+
 When tracing is enabled, the Sentry SDK will not only create spans for pageloads and transactions but also propagate trace information to other systems. This allows you to connect multiple systems and see how they interact with each other.
 
-If you have not enabled tracing, or you need to propagate traces in places other than outgoing HTTP requests (e.g. when working with websockers), you can manually set up your application for distributed tracing to work.
+By default, outgoing HTTP requests will automatically be instrumented for you. For other cases where you may want to continue traces (for example when working with websockets), you can manually extract and inject tracing information.
 
 ## Enabling Automatic Distributed Tracing
 
 To enable distributed tracing for your frontend, add `browserTracingIntegration` to your `Sentry.init()` options as described in the <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/">Automatic Instrumentation</PlatformLink> docs.
 
-If you want to use distributed tracing without creating spans, set the `tracesSampleRate` option to `0`.
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-  integrations: [Sentry.browserTracingIntegration()],
-
-  // If this is 0, tracing is disabled
-  // but distributed tracing is not
-  tracesSampleRate: 0,
-});
-```
-
 ### Continuing a Trace Manually
 
 By default, the `browserTracingIntegration` will automatically continue a trace found in a `<meta>` tag - see <PlatformLink to="/tracing/trace-propagation/#automatic-trace-propagation">Automatic Trace Propagation</PlatformLink> for details.
@@ -53,7 +43,7 @@ Sentry.startBrowserTracingPageLoadSpan(
 
 ## Configuring Distributed Tracing Without `browserTracingIntegration`
 
-If you don't want to use the `browserTracingIntegration` integration, you can manually extract and inject tracing data in your application to connect multiple systems. For this, you must:
+If you don't want to use the `browserTracingIntegration` integration, or you want to propagate traces in other places than HTTP requests (for example, with websockets), you can manually extract and inject tracing data in your application to connect multiple systems. For this, you must:
 
 - Extract and store incoming tracing information from HTML `<meta>` tags when loading the page.
 - Inject tracing information to any outgoing requests.

platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx

@@ -1,17 +1,9 @@
 Trace propagation is set up automatically in this SDK. By default, outgoing HTTP requests will automatically be instrumented for you.
-For other cases where you may want to continue traces (for example, in a job queue or when working with web sockets), you can manually extract and inject tracing information.
+For other cases where you may want to continue traces (for example, in a job queue or when working with websockets), you can manually extract and inject tracing information.
 
-If you want to use distributed tracing without creating spans, set the `tracesSampleRate` option to `0`.
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // If this is 0, tracing is disabled
-  // but distributed tracing is not
-  tracesSampleRate: 0,
-});
-```
+<Expandable title="What is Distributed Tracing?">
+  <PlatformContent includePath="distributed-tracing/explanation" />
+</Expandable>
 
 ## Manually Extracting and Injecting Distributed Tracing Information
 

platform-includes/distributed-tracing/explanation/javascript.mdx

@@ -0,0 +1,3 @@
+In the context of tracing events across a distributed system, distributed tracing acts as a powerful debugging tool. Imagine your application as a vast network of interconnected parts. For example, your system might be spread across different servers or your application might split into different backend and frontend services, each potentially having their own technology stack.
+
+When an error or performance issue occurs, it can be challenging to pinpoint the root cause due to the complexity of such a system. Distributed tracing helps you follow the path of an event as it travels through this intricate web, recording every step it takes. By examining these traces, you can reconstruct the sequence of events leading up to the event of interest, identify the specific components involved, and understand their interactions. This detailed visibility enables you to diagnose and resolve issues more effectively, ultimately improving the reliability and performance of your distributed system.