First content pass

Author: Alex Krawiec

docs/product/explore/metrics/index.mdx

@@ -1,18 +1,18 @@
 ---
 title: "Metrics"
 sidebar_order: 75
-description: "Send counters, gauges, and distributions from your code to track application health and pivot directly into related traces, logs, and errors."
+description: "Send counters, gauges, and distributions from your code to track application health and drill down into related traces, logs, and errors."
 ---
 
 <Alert level="info">
-  Metrics is currently in beta. If you'd like access for JavaScript or Python, please comment with your org slug on [this GitHub discussion](https://github.com/getsentry/sentry/discussions/102275) or contact us at [email protected].
+  Metrics is currently in Open Beta for non-Enterprise plans runing the JavaScript or Python SDKs. If you'd like access, please comment with your org slug on [this GitHub discussion](https://github.com/getsentry/sentry/discussions/102275) or contact us at [email protected].
 </Alert>
 
 ## Overview
 
-With Sentry Metrics, you can send counters, gauges, and distributions from your code to track application health signals like `email.sent`, `checkout.failed`, or `queue.depth`. What makes Sentry's Metrics unique is that every metric event is **trace-connected**, meaning you can pivot directly into the related traces, logs, and errors when something looks off.
+With Sentry Metrics, you can send counters, gauges, and distributions from your code to track application health signals like `email.sent`, `checkout.failed`, or `queue.depth`. What makes Sentry's Metrics unique is that every metric event is **trace-connected**, meaning you can click directly into the related traces, logs, and errors when something looks off.
 
-Unlike traditional metrics tools that only show _that_ something changed, Sentry's trace-connected metrics let you understand _why_ it changed. When a `checkout.failed` counter spikes, you can click into a sample and see the exact trace, spans, logs, and errors that produced that metric event.
+Unlike traditional metrics tools that only show _if_ something's changed, Sentry's trace-connected metrics let you understand _why_ it changed. When a `checkout.failed` counter spikes, you can click into a sample and see the exact trace, spans, logs, and errors that produced that metric event.
 
 Not everything in your application generates an error or requires full tracing. Metrics are perfect for tracking:
 
@@ -29,7 +29,7 @@ To get started with Metrics, navigate to the [Getting Started](/product/explore/
 
 Sentry supports three types of metrics:
 
-### Counter
+### Counters
 
 Counters track how many times something happened. Each increment adds to a cumulative total.
 
@@ -38,7 +38,7 @@ Counters track how many times something happened. Each increment adds to a cumul
 - `checkout.failed` - Track failed checkout attempts
 - `api.request` - Track API calls
 
-### Gauge
+### Gauges
 
 Gauges set a specific value at a point in time, like a snapshot. The latest value replaces the previous one.
 
@@ -47,7 +47,7 @@ Gauges set a specific value at a point in time, like a snapshot. The latest valu
 - `pool.in_use` - Active connections in a pool
 - `memory.usage` - Current memory consumption
 
-### Distribution
+### Distributions
 
 Distributions record numeric values to compute statistical aggregates like p50, p95, average, and sum.
 

redirects.js

@@ -1063,10 +1063,6 @@ const userDocsRedirects = [
     source: '/product/explore/feature-flags/:path*',
     destination: '/product/issues/issue-details/feature-flags/:path*',
   },
-  {
-    source: '/product/explore/metrics/:path*',
-    destination: '/concepts/key-terms/tracing/span-metrics/',
-  },
   {
     source: '/product/tracing/:path*',
     destination: '/concepts/key-terms/tracing/:path*',