Add more fixes from the review

elastic · Jan 8, 2020 · b7ccf86 · b7ccf86
1 parent 7bcbe5b
commit b7ccf86
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 4 deletions.
diff --git a/libbeat/docs/monitoring/monitoring-internal-collection.asciidoc b/libbeat/docs/monitoring/monitoring-internal-collection.asciidoc
@@ -18,10 +18,11 @@
 
 Use internal collectors to send {beats} monitoring data directly to your
 monitoring cluster.
-
 ifndef::serverless[]
 Or as an alternative to internal collection, use
-<<monitoring-metricbeat-collection>>.
+<<monitoring-metricbeat-collection>>. The benefit of using internal collection
+instead of {metricbeat} is that you have fewer pieces of software to install
+and maintain.
 endif::[]
 
 //Commenting out this link temporarily until the general monitoring docs can be

diff --git a/libbeat/docs/monitoring/monitoring-metricbeat.asciidoc b/libbeat/docs/monitoring/monitoring-metricbeat.asciidoc
@@ -7,7 +7,9 @@
 ++++
 
 In 7.3 and later, you can use {metricbeat} to collect data about {beatname_uc} 
-and ship it to the monitoring cluster.
+and ship it to the monitoring cluster. The benefit of using {metricbeat} instead
+of internal collection is that the monitoring agent remains active even if the
+{beatname_uc} instance dies.
 
 ifeval::["{beatname_lc}"=="metricbeat"]
 Because you'll be using {metricbeat} to _monitor_ {beatname_uc}, you'll need to

diff --git a/libbeat/docs/monitoring/shared-monitor-config-legacy.asciidoc b/libbeat/docs/monitoring/shared-monitor-config-legacy.asciidoc
@@ -69,7 +69,7 @@ Custom HTTP headers to add to each request. For more information, see
 ==== `hosts`
 
 The list of {es} nodes to connect to. Monitoring metrics are distributed to
-these nodes in round robin order. For more information, see
+these nodes in round-robin order. For more information, see
 <<elasticsearch-output>>.
 
 [float]