diff --git a/docs/product/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx
index ac17838549bc6..e69142ba4fba9 100644
--- a/docs/product/alerts/alert-types.mdx
+++ b/docs/product/alerts/alert-types.mdx
@@ -37,9 +37,7 @@ The **Alert Details** page also includes a list of issues that triggered the ale
Metric alerts tell you when a [metric](/product/performance/metrics/) crosses a threshold set by you, like a spike in the number of errors in a project, or a change in a performance metric, such as [transaction duration](/product/performance/metrics/#latency), [Apdex](/product/performance/metrics/#apdex), [failure rate](/product/performance/metrics/#failure-rate), or [throughput](/product/performance/metrics/#throughput-total-tpm-tps).
-
You can use [dynamic alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) to let Sentry define the threshold for you.
-
Metric alerts monitor macro-level metrics for both error and transaction events. A metric takes a set of events and computes an aggregate value using a function, such as `count()` or `avg()`, applied to the event properties over a period of time. When you create a metric alert, you can filter events by attributes and tags, which is particularly useful for aggregating across events that aren't grouped into single issues. Sentry allows a maximum of 1000 metric alerts for an organization.
diff --git a/docs/product/alerts/create-alerts/metric-alert-config.mdx b/docs/product/alerts/create-alerts/metric-alert-config.mdx
index 865ff4606710b..dd13cc6a57eed 100644
--- a/docs/product/alerts/create-alerts/metric-alert-config.mdx
+++ b/docs/product/alerts/create-alerts/metric-alert-config.mdx
@@ -115,9 +115,9 @@ While Sentry won’t allow you to create new alerts with invalid or unavailable
There are three threshold types:
-- **Static**: A fixed threshold, such as when there are 100 errors in a period of time.
-- **Percent change**: A percent-based threshold, such as when there are 10% more errors in a time period compared to a previous period. These are also referred to as [Change Alerts](#change-alerts-percent-change).
-- **Dynamic**: A dynamic threshold set by Sentry that detects anomalies whenever values fall outside expected bounds.
+- **Static**: A fixed numerical threshold set by you. (For example, if there are 100 errors in a set period of time.)
+- **Percent change**: A percent-based threshold set by you. (For example, if 10% more errors are detected in a time period compared to a previous period.) These are also referred to as [Change Alerts](#change-alerts-percent-change).
+- **Dynamic**: A dynamic threshold set by Sentry that detects anomalies whenever values fall outside of expected bounds.
By default, metric alerts use a fixed threshold.
@@ -133,9 +133,9 @@ Change alerts, or alerts that use a percent change threshold, are useful when yo
-Dynamic alerts can be used when you don't know what threshold to set, but you know you want to be alerted when something is far outside the bounds of normalcy. Sentry will look at the historical data for the given metric and determine if the current data is anomalous. You can select how responsive the alert will be, and whether you want to be alerted when the metric is above and/or below the expected bounds.
+Dynamic alerts can be used when you're not sure about what threshold to set, but want to be alerted when something is far outside the bounds of normalcy. To determine what is and isn't normal, Sentry will look at the historical data for the given metric and compare it to the current data to see if it's anomalous. You can select how responsive the alert will be, and whether you want to be alerted when the metric is above and/or below the expected bounds.
-Dynamic alerts do not use the Critical, Warning, and Resolved thresholds. When no more anomalies are detected, the alert will resolve on its own.
+Dynamic alerts don't use the Critical, Warning, and Resolved thresholds. When no more anomalies are detected, the alert will resolve on its own.
