From dca17766a42dd797eefa685c1a4fe4170b56ee5b Mon Sep 17 00:00:00 2001
From: Dario Gieselaar <dario.gieselaar@elastic.co>
Date: Wed, 17 Feb 2021 14:41:57 +0100
Subject: [PATCH] [DOCS] Remove keyword/ip from list of unsupported fields in
 top_metrics agg (#69036)

---
 .../aggregations/metrics/top-metrics-aggregation.asciidoc      | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc b/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc
index 7226f76cfe9eb..22a743b1de8c1 100644
--- a/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc
+++ b/docs/reference/aggregations/metrics/top-metrics-aggregation.asciidoc
@@ -54,8 +54,7 @@ faster.
 The `sort` field in the metric request functions exactly the same as the `sort` field in the
 <<sort-search-results, search>> request except:
 
-* It can't be used on <<binary,binary>>, <<flattened,flattened>>, <<ip,ip>>,
-<<keyword,keyword>>, or <<text,text>> fields.
+* It can't be used on <<binary,binary>>, <<flattened,flattened>> or <<text,text>> fields.
 * It only supports a single sort value so which document wins ties is not specified.
 
 The metrics that the aggregation returns is the first hit that would be returned by the search