diff --git a/docs/user/alerting/rule-types.asciidoc b/docs/user/alerting/rule-types.asciidoc
index bcab22f05ca0..4791dd4521c5 100644
--- a/docs/user/alerting/rule-types.asciidoc
+++ b/docs/user/alerting/rule-types.asciidoc
@@ -39,7 +39,7 @@ see {subscriptions}[the subscription page].
 [[observability-rules]]
 === {observability} rules
 
-{observability} rules are categorized into APM and {user-experience}, Logs, Metrics, {stack-monitor-app}, and Uptime.
+{observability} rules detect complex conditions in your observability data and create alerts when a rule's conditions are met. For example, you can create a rule that detects when the value of a metric exceeds a specified threshold or when an anomaly occurs on a system or service you are monitoring. For more information, refer to {observability-guide}/create-alerts.html[Alerting].
 
 [NOTE]
 ==============================================
@@ -47,27 +47,6 @@ If you create a rule in the {observability} app, its alerts are not visible in
 *{stack-manage-app} > {rules-ui}*. They are visible only in the {observability} app.
 ==============================================
 
-[cols="2*<"]
-|===
-
-
-| <<apm-alerts, APM and User Experience>>
-| Detect complex conditions in *APM* data and trigger built-in actions when the conditions are met.
-
-| {observability-guide}/logs-threshold-alert.html[Logs rules]
-| Detect complex conditions in the {logs-app}.
-
-| {observability-guide}/metrics-threshold-alert.html[Metrics rules]
-| Detect complex conditions in the {metrics-app}.
-
-| {observability-guide}/slo-burn-rate-alert.html[SLO burn rate rule]
-| Detect when the burn rate is above a defined threshold.
-
-| {observability-guide}/monitor-status-alert.html[Uptime rules]
-| Detect complex conditions in the {uptime-app}.
-
-|===
-
 [float]
 [[ml-rules]]
 === Machine learning rules