diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc
index 2e678b929d29..89eb6e855905 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 f7ebcb3716b8..000000000000
Binary files a/docs/reference/ml/images/ml-rule.png and /dev/null differ
diff --git a/docs/reference/transform/images/transform-rule.png b/docs/reference/transform/images/transform-rule.png
deleted file mode 100644
index c43dd6c1be92..000000000000
Binary files a/docs/reference/transform/images/transform-rule.png and /dev/null differ
diff --git a/docs/reference/transform/transform-alerts.asciidoc b/docs/reference/transform/transform-alerts.asciidoc
index e3ea82d34ec2..988dc5effe95 100644
--- a/docs/reference/transform/transform-alerts.asciidoc
+++ b/docs/reference/transform/transform-alerts.asciidoc
@@ -18,18 +18,19 @@ refer to
 
 You can create {transform} rules under **{stack-manage-app} > {rules-ui}**.
 
-. On the *Create rule* window, give a name to the rule and optionally provide 
-tags. Select the {transform} health rule type:
-+
---
-[role="screenshot"]
-image::images/transform-rule.png["Creating a transform health rule",500]
-// NOTE: This is screenshot is automatically generated. Do not edit it directly.
---
+. Click *Create rule* and select the {transform} health rule type.
+
+. Give a name to the rule and optionally provide tags.
 
 . Select the {transform} or {transforms} to include. You can also use a special 
 character (`*`) to apply the rule to all your {transforms}. {transforms-cap} 
 created after the rule are automatically included.
++
+--
+[role="screenshot"]
+image::images/transform-check-config.png["Selecting health check",500]
+// NOTE: This is screenshot is automatically generated. Do not edit it directly.
+--
 
 . The following health checks are available and enabled by default:
 +
@@ -41,10 +42,6 @@ _{transform-cap} is not started_::
 _Unhealthy {transform}_:: 
   Get alerts when a {transform} has an unhealthy status.
   The notification message contains status details and related issues.
-
-[role="screenshot"]
-image::images/transform-check-config.png["Selecting health check",500]
-// NOTE: This is screenshot is automatically generated. Do not edit it directly.
 --
 
 . Set the check interval, which defines how often to evaluate the rule conditions.