diff --git a/docs/user/monitoring/images/monitoring-kibana-alerts.png b/docs/user/monitoring/images/monitoring-kibana-alerts.png
deleted file mode 100644
index 43edcb450414..000000000000
Binary files a/docs/user/monitoring/images/monitoring-kibana-alerts.png and /dev/null differ
diff --git a/docs/user/monitoring/kibana-alerts.asciidoc b/docs/user/monitoring/kibana-alerts.asciidoc
index 6046e67db62f..ccd023f180c9 100644
--- a/docs/user/monitoring/kibana-alerts.asciidoc
+++ b/docs/user/monitoring/kibana-alerts.asciidoc
@@ -9,7 +9,7 @@ best practices recommended by Elastic. However, you can tailor them to meet your
 specific needs.
 
 [role="screenshot"]
-image::user/monitoring/images/monitoring-kibana-alerts.png["{kib} alerts in {stack-monitor-app}"]
+image::user/monitoring/images/monitoring-kibana-alerting-notification.png["{kib} alerting notifications in {stack-monitor-app}"]
 
 When you open *{stack-monitor-app}*, the preconfigured rules are created 
 automatically. They are initially configured to detect and notify on various 
@@ -23,9 +23,8 @@ been recreated as rules in {kib} {alert-features}. For this reason, the existing
 The default action for all {stack-monitor-app} rules is to write to {kib} logs 
 and display a notification in the UI.
 
-[role="screenshot"]
-image::user/monitoring/images/monitoring-kibana-alerting-notification.png["{kib} alerting notifications in {stack-monitor-app}"]
-
+To review and modify all available rules, use *Enter setup mode* on the 
+*Cluster overview* page in *{stack-monitor-app}*:
 
 [role="screenshot"]
 image::user/monitoring/images/monitoring-kibana-alerting-setup-mode.png["Modify {kib} alerting rules in {stack-monitor-app}"]