diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc
index 2e678b929d296..89eb6e8559056 100644
--- a/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc
+++ b/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc
@@ -27,12 +27,7 @@ TIP: If you have created rules for specific {anomaly-jobs} and you want to
 monitor whether these jobs work as expected, {anomaly-jobs} health rules are 
 ideal for this purpose.
 
-In *{stack-manage-app} > {rules-ui}*, you can create both types of {ml} rules:
-
-[role="screenshot"]
-image::images/ml-rule.png["Creating a new machine learning rule",500]
-// NOTE: This is an autogenerated screenshot. Do not edit it directly.
-
+In *{stack-manage-app} > {rules-ui}*, you can create both types of {ml} rules.
 In the *{ml-app}* app, you can create only {anomaly-detect} alert rules; create
 them from the {anomaly-job} wizard after you start the job or from the
 {anomaly-job} list.
diff --git a/docs/reference/ml/images/ml-rule.png b/docs/reference/ml/images/ml-rule.png
deleted file mode 100644
index f7ebcb3716b81..0000000000000
Binary files a/docs/reference/ml/images/ml-rule.png and /dev/null differ