Reordering distributed tracing for faster steps to configure

Author: codyde

docs/platforms/javascript/common/tracing/distributed-tracing/index.mdx

@@ -27,6 +27,16 @@ What happens in the background is that Sentry uses reads and further propagates
 
 If you run any JavaScript applications in your distributed system, make sure that those two headers are added to your CORS allowlist and won't be blocked or stripped by your proxy servers, gateways, or firewalls.
 
+## How to Use Distributed Tracing?
+
+<PlatformContent includePath="distributed-tracing/how-to-use/" />
+
+<Alert >
+
+Remember that in order to propagate trace information through your whole distributed system, you have to use Sentry in all of the involved services and applications. Take a look at the respective SDK documentation to learn how distributed tracing can be enabled for each platform.
+
+</Alert>
+
 ## Trace Duration
 
 <PlatformCategorySection supported={["browser"]}>
@@ -50,13 +60,3 @@ Server-side SDKs handle traces automatically on a per-request basis. This means
 </PlatformCategorySection>
 
 If necessary, you can override the default trace duration by [manually starting a new trace](./custom-instrumentation#starting-a-new-trace).
-
-## How to Use Distributed Tracing?
-
-<PlatformContent includePath="distributed-tracing/how-to-use/" />
-
-<Alert >
-
-Remember that in order to propagate trace information through your whole distributed system, you have to use Sentry in all of the involved services and applications. Take a look at the respective SDK documentation to learn how distributed tracing can be enabled for each platform.
-
-</Alert>