From c4855598cc57f07e3dafa6fe74cc7bdf3a416d01 Mon Sep 17 00:00:00 2001 From: elasticsearchmachine <58790826+elasticsearchmachine@users.noreply.github.com> Date: Wed, 28 Jul 2021 14:50:20 -0400 Subject: [PATCH] [DOCS] Fixes bulleted list in ML aggregations (#75806) (#75808) Co-authored-by: Lisa Cawley --- .../ml/anomaly-detection/ml-configuring-aggregations.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc index 7970eacff6407..85de5d1254133 100644 --- a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc +++ b/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc @@ -425,10 +425,11 @@ When using a `composite` aggregation: // NOTCONSOLE The top level aggregation must be exclusively one of the following: + * A {ref}/search-aggregations-bucket.html[bucket aggregation] containing a single sub-aggregation that is a `date_histogram` * A top level aggregation that is a `date_histogram` -* A top level aggregation is a `composite` aggregation. +* A top level aggregation is a `composite` aggregation There must be exactly one `date_histogram`, `composite` aggregation. For more information, see {ref}/search-aggregations-bucket-datehistogram-aggregation.html[Date histogram aggregation] and