diff --git a/docs/en/observability/images/inventory-alert.png b/docs/en/observability/images/inventory-alert.png
index a0508106d5..07dd30edd1 100644
Binary files a/docs/en/observability/images/inventory-alert.png and b/docs/en/observability/images/inventory-alert.png differ
diff --git a/docs/en/observability/inventory-threshold-alert.asciidoc b/docs/en/observability/inventory-threshold-alert.asciidoc
index ea0cedb463..041921c5ec 100644
--- a/docs/en/observability/inventory-threshold-alert.asciidoc
+++ b/docs/en/observability/inventory-threshold-alert.asciidoc
@@ -35,16 +35,12 @@ You can also set advanced options such as the number of consecutive runs that mu
 In this example, Kubernetes Pods is the selected inventory type. The conditions state that you will receive
 a critical alert for any pods within the `ingress-nginx` namespace with a memory usage of 95% or above
 and a warning alert if memory usage is 90% or above.
+The chart shows the results of applying the rule to the last 20 minutes of data.
+Note that the chart time range is 20 times the value of the look-back window specified in the `FOR THE LAST` field.
 
 [role="screenshot"]
 image::images/inventory-alert.png[Inventory rule]
 
-Before creating a rule, you can preview whether the conditions would have triggered the alert in the last
-hour, day, week, or month.
-
-[role="screenshot"]
-image::images/alert-preview.png[Preview rules]
-
 [discrete]
 [[action-types-infrastructure]]
 == Action types