diff --git a/docs/en/observability/images/slo-action-frequency.png b/docs/en/observability/images/slo-action-frequency.png
new file mode 100644
index 0000000000..cef8d4307e
Binary files /dev/null and b/docs/en/observability/images/slo-action-frequency.png differ
diff --git a/docs/en/observability/images/slo-action-variables.png b/docs/en/observability/images/slo-action-variables.png
new file mode 100644
index 0000000000..5441c5cc53
Binary files /dev/null and b/docs/en/observability/images/slo-action-variables.png differ
diff --git a/docs/en/observability/slo-burn-rate-alert.asciidoc b/docs/en/observability/slo-burn-rate-alert.asciidoc
index 44d082d52e..359809633f 100644
--- a/docs/en/observability/slo-burn-rate-alert.asciidoc
+++ b/docs/en/observability/slo-burn-rate-alert.asciidoc
@@ -37,15 +37,12 @@ You can configure action types on the <<configure-uptime-alert-connectors,Settin
 [role="screenshot"]
 image::images/alert-action-types.png[Uptime rule connectors]
 
-After you select a connector, you must set the action frequency. You can choose to create a summary of alerts on each check interval or on a custom interval. For example, send email notifications that summarize the new, ongoing, and recovered alerts every twelve hours:
+After you select a connector, you must set the action frequency. You can choose to create a *Summary of alerts* on each check interval or on a custom interval. For example, you can send email notifications that summarize the new, ongoing, and recovered alerts every twelve hours.
 
-[role="screenshot"]
-image::images/duration-anomaly-alert-summary.png[Action types]
-
-Alternatively, you can set the action frequency such that you choose how often the action runs (for example, at each check interval, only when the alert status changes, or at a custom action interval). In this case, you must also select the specific threshold condition that affects when actions run: `Uptime Duration Anomaly` or `Recovered`.
+Alternatively, you can set the action frequency to *For each alert* and specify the conditions each alert must meet for the action to run. For example, you can send an email only when the alert status changes to critical.
 
 [role="screenshot"]
-image::images/duration-anomaly-run-when-selection.png[Configure when a rule is triggered]
+image::images/slo-action-frequency.png[Configure when a rule is triggered]
 
 [discrete]
 [[action-variables-slo]]
@@ -56,8 +53,7 @@ You can add more context to the message by clicking the icon above the message t
 and selecting from a list of available variables.
 
 [role="screenshot"]
-image::images/duration-anomaly-alert-default-message.png[Default notification message for Uptime duration anomaly rules with open "Add variable" popup listing available action variables,width=600]
-
+image::images/slo-action-variables.png[Action variables with default SLO message]
 
 [discrete]
 [[recovery-variables-slo]]