From 1df7941f6e9ead235001dd4eb85d90e33389a2fe Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Mon, 11 Dec 2023 09:51:49 -0500 Subject: [PATCH] Address review comments --- .../fleet/fleet-settings-output-elasticsearch.asciidoc | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/docs/en/ingest-management/fleet/fleet-settings-output-elasticsearch.asciidoc b/docs/en/ingest-management/fleet/fleet-settings-output-elasticsearch.asciidoc index f7f0ab3d4..dc952257e 100644 --- a/docs/en/ingest-management/fleet/fleet-settings-output-elasticsearch.asciidoc +++ b/docs/en/ingest-management/fleet/fleet-settings-output-elasticsearch.asciidoc @@ -88,9 +88,9 @@ Sending monitoring data to a remote {es} cluster is currently not supported. [id="es-agent-performance-tuning"] **Performance tuning** -| Choose one of the menu options to tune your {agent} performace when sending data to an {es} output. You can optimize for throughput, scale, latency, or you can choose a balanced (the default) set of performance specifications. Refer to <> for details about the setting values and their potential impact on performance. +| Choose one of the menu options to tune your {agent} performance when sending data to an {es} output. You can optimize for throughput, scale, latency, or you can choose a balanced (the default) set of performance specifications. Refer to <> for details about the setting values and their potential impact on performance. -You can also use the <> field to set custom values. Note that if you adjust performance settings through the advanced YAML configuration, the **Performance tuning** option automatically changes to `Custom`. +You can also use the <> field to set custom values. Note that if you adjust any of the performance settings described in the following **Advanced YAML configuration** section, the **Performance tuning** option automatically changes to `Custom` and cannot be changed. |=== [[es-output-settings-yaml-config]] @@ -199,12 +199,6 @@ For descriptions of each setting, refer to <