Merge branch 'codyde/javascript-tracing-refactor' of https://github.com/getsentry/sentry-docs into codyde/javascript-tracing-refactor

* 'codyde/javascript-tracing-refactor' of https://github.com/getsentry/sentry-docs:
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/span-metrics/index.mdx
  Update docs/platforms/javascript/common/tracing/span-metrics/index.mdx
  Update docs/platforms/javascript/common/tracing/span-metrics/index.mdx
  Update docs/product/tracing/span-metrics/index.mdx
  Update docs/platforms/javascript/common/tracing/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/instrumentation/index.mdx
  Update docs/platforms/javascript/common/tracing/index.mdx

Author: codyde

docs/concepts/key-terms/tracing/span-metrics.mdx

@@ -69,7 +69,7 @@ There are two primary methods for implementing span metrics:
 
 ### 1. Enhancing Existing Spans
 
-Augment automatically created or manually defined spans with additional metric attributes:
+Augment automatically-created or manually-defined spans with additional metric attributes:
 
 ```javascript
 // Adding metrics to an existing file upload span

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

@@ -40,7 +40,7 @@ With [tracing](/product/insights/overview/), Sentry automatically tracks your so
 
 <PlatformContent includePath="performance/configure-sample-rate" />
 
-- You can set a uniform sample rate for all transactions using the <PlatformIdentifier name="traces-sample-rate" /> option in your SDK config to a number between `0` and `1`. (For example, to send 20% of transactions, set <PlatformIdentifier name="traces-sample-rate" /> to `0.2`.)
+- You can establish a uniform sample rate for all transactions by setting the <PlatformIdentifier name="traces-sample-rate" /> option in your SDK config to a number between `0` and `1`. (For example, to send 20% of transactions, set <PlatformIdentifier name="traces-sample-rate" /> to `0.2`.)
 - For more granular control over sampling, you can set the sample rate based on the transaction itself and the context in which it's captured, by providing a function to the <PlatformIdentifier name="traces-sampler" /> config option.
 
 The two options are mutually exclusive. If both are set, <PlatformIdentifier name="traces-sampler" /> will take precedence.
@@ -49,7 +49,7 @@ Learn more about tracing <PlatformLink to="/configuration/options/#tracing-optio
 
 ## Distributed Tracing
 
-Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
+Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services, respectively. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
 
  <PlatformSection notSupported={["javascript.bun", "javascript.deno", "javascript.cloudflare", "javascript.cordova", "javascript.capacitor"]}>

docs/platforms/javascript/common/tracing/instrumentation/index.mdx

@@ -18,7 +18,7 @@ To get started, import the SDK.
 
 There are three key functions for creating spans:
 
-- [startSpan](#starting-an-active-span-startspan): Creates a new span that is active, and which is automatically ended. You'll likely want to use this function.
+- [startSpan](#starting-an-active-span-startspan): Creates a new span that is active, and which will end automatically. You'll likely want to use this function.
 - [startSpanManual](#starting-an-active-span-with-manual-end-startspanmanual): Creates a new span that is active, which has to be ended manually.
 - [startInactiveSpan](#starting-inactive-spans-startinactivespan): Creates a new span that is inactive, which has to be ended manually.
 
@@ -30,7 +30,7 @@ In contrast, **inactive spans** will never have children automatically associate
 
 A key constraint for active spans is that they can only be made active inside of a callback. This constraint exists because otherwise it becomes impossible to associate spans with the correct parent span when working with asynchronous code.
 
-In places where you are not able to wrap executing code in a callback (e.g. when working with hooks or similar) you have to work with inactive spans, and can combine this with [withActiveSpan](#withactivespan) to manually associate child spans with the correct parent span.
+In places where you are not able to execute your code in a callback (for example, when working with hooks or similar) you have to work with inactive spans, and can combine this with [withActiveSpan](#withactivespan) to manually associate child spans with the correct parent span.
 
 <PlatformCategorySection supported={['browser']}>
 
@@ -86,7 +86,7 @@ Only `name` is required, all other options are optional.
 
 ## Starting an Active Span (`startSpan`)
 
-For most scenarios, we recommend to start active spans with `Sentry.startSpan()`. This will start a new span that is active in the provided callback, and will automatically end the span when the callback is done. The callback can be synchronous, or asynchronous (a promise). In the case of an asynchronous callback, the span will be ended when the promise is resolved or rejected. If the provided callback errors or rejects, the span will be marked as failed.
+For most scenarios, we recommend to start active spans with `Sentry.startSpan()`. This will start a new span that is active in the provided callback, and will automatically end the span when the callback is done. The callback can be synchronous or asynchronous (a promise). In the case of an asynchronous callback, the span will be ended when the promise is resolved or rejected. If the provided callback throws an error or rejects a promise, the span will be marked as failed.
 
 <PlatformContent includePath="performance/start-span" />
 
@@ -116,7 +116,7 @@ parentSpan.end();
 
 This option is also available for `startSpan` and `startSpanManual`.
 
-## Utilities to work with Spans
+## Utilities To Work With Spans
 
 We expose some helpful utilities that can help you with custom instrumentation.
 
@@ -175,7 +175,7 @@ const childSpan = Sentry.startInactiveSpan({
 
 ### `suppressTracing`
 
-Suppress the creation of sampled spans for the duration of the callback. This is useful when you want to prevent certain spans from being captured. For example, if you do not want to create spans for a given fetch request, you can do:
+Suppresses the creation of sampled spans for the duration of the callback. This is useful when you want to prevent certain spans from being captured. For example, if you do not want to create spans for a given fetch request, you can do:
 
 ```javascript
 Sentry.suppressTracing(() => {
@@ -255,9 +255,9 @@ Sentry.init({
 
 ### Adding Span Operations ("op")
 
-Spans can have an operation associated with them, which help activate Sentry identify additional context about the span. For example database related spans have the `db` span operation associated with them. The Sentry product offers additional controls, visualizations and filters for spans with known operations.
+Spans can have an operation associated with them, which help Sentry identify additional context about the span. For example, database related spans have the `db` span operation associated with them. The Sentry product offers additional controls, visualizations, and filters for spans with known operations.
 
-Sentry maintains a [list of well known span operations](https://develop.sentry.dev/sdk/performance/span-operations/#list-of-operations) and it is recommended that you use one of those operations if it is applicable to your span.
+Sentry maintains a [list of well-known span operations](https://develop.sentry.dev/sdk/performance/span-operations/#list-of-operations) and it is recommended that you use one of those operations if it is applicable to your span.
 
 <PlatformContent includePath="performance/span-operations" />
 

docs/platforms/javascript/common/tracing/span-metrics/index.mdx

@@ -41,7 +41,7 @@ When adding metrics as span attributes:
 
 - Use consistent naming conventions (for example, `category.metric_name`)
 - Keep attribute names concise but descriptive
-- Use appropriate data types (string, number, boolean, or arrays of these types)
+- Use appropriate data types (string, number, boolean, or (non-mixed) arrays of these types)
 
 ## Creating Dedicated Metric Spans
 
@@ -100,7 +100,7 @@ Sentry.init({
 
 1. **Metric Naming**
    - Use clear, consistent naming patterns
-   - Include the metric category (e.g., `db`, `cache`, `http`)
+   - Include the metric category (examples: `db`, `cache`, `http`)
    - Use snake_case for metric names
    - Avoid high-cardinality values in metric names
 
@@ -139,6 +139,6 @@ When implementing span metrics in your application:
 3. **Focus on Actionability**
    - Track metrics that help diagnose specific issues
    - Consider what alerts or dashboard visualizations you'll want to create
-   - Ensure metrics can drive issue resolution or decision-making
+   - Ensure metrics can drive issue resolution or decision making
 
 For detailed examples of how to implement span metrics in common scenarios, see our <PlatformLink to="/tracing/span-metrics/examples/">Span Metrics Examples</PlatformLink> guide.