diff --git a/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc b/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc
index 5326b8567..d338f9101 100644
--- a/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc
+++ b/docs/en/stack/ml/anomaly-detection/anomaly-detection-scale.asciidoc
@@ -65,7 +65,7 @@ size of a {ml} node. Creating {ml-jobs} with model memory limits larger than the
 maximum node size can support is not allowed, as autoscaling cannot add a node 
 big enough to run the job. On a self-managed deployment, you can set 
 `xpack.ml.max_model_memory_limit` according to the available resources of the 
-{ml} node. This prevents you from you creating jobs with model memory limits too 
+{ml} node. This prevents you from creating jobs with model memory limits too 
 high to open in your cluster.
 
 [discrete]