Edits following review

filebeat/docs/running-on-kubernetes.asciidoc

@@ -115,19 +115,12 @@ don't run this command, the default node selector will skip master nodes.
 [float]
 ==== Load {kib} dashboards
 
-{beatname_uc} comes packaged with example {kib} dashboards,
-visualizations, and searches for visualizing {beatname_uc} data in {kib}.
+{beatname_uc} comes packaged with various pre-built {kib} dashboards
+that you can use to visualize logs from your Kubernetes environment.
 
-
-Before you can use the dashboards, you need to create the index pattern,
-+{beatname_lc}-*+, and load the dashboards into {kib}. To do this, run the `setup`
-command to load the recommended {ref}/indices-templates.html[index template]
-for writing to {es} and to deploy the sample dashboards for visualizing the data in {kib}.
-For details, see <<load-kibana-dashboards>>.
-
-Otherwise, you can
-<<configuration-dashboards,configure dashboard loading>> in the
-+{beatname_lc}.yml+ config file.
+If these dashboards are not already loaded into {kib}, you must <<{beatname_lc}-installation-configuration,install {beatname_uc}>>
+on any system that can connect to the {stack}, and then run the `setup` command to load the dashboards.
+To learn how, see <<load-kibana-dashboards,Load {kib} dashboards>>.
 
 The `setup` command does not load the ingest pipelines used to parse log lines. By default, ingest pipelines
 are set up automatically the first time you run {beatname_uc} and connect to {es}.
@@ -142,7 +135,6 @@ need to:
 * <<load-ingest-pipelines>>
 =======================================
 
-
 [float]
 ==== Deploy
 

libbeat/docs/shared-cloudfoundry.asciidoc

@@ -55,18 +55,11 @@ You need to modify the +{beatname_lc}.yml+ file to set the `api_address`,
 
 ==== Load {kib} dashboards
 
-{beatname_uc} comes packaged with example {kib} dashboards,
-visualizations, and searches for visualizing {beatname_uc} data in {kib}.
-
-Before you can use the dashboards, you need to create the index pattern,
-+{beatname_lc}-*+, and load the dashboards into {kib}. To do this, run the `setup`
-command to load the recommended {ref}/indices-templates.html[index template]
-for writing to {es} and to deploy the sample dashboards for visualizing the data in {kib}.
-For details, see <<load-kibana-dashboards>>.
-
-Otherwise, you can
-<<configuration-dashboards,configure dashboard loading>> in the
-+{beatname_lc}.yml+ config file.
+{beatname_uc} comes packaged with various pre-built {kib} dashboards
+that you can use to visualize data in {kib}.
+
+If these dashboards are not already loaded into {kib}, you must run the {beatname_uc} `setup` command.
+To learn how, see <<load-kibana-dashboards,Load {kib} dashboards>>.
 
 ifeval::["{beatname_lc}"=="metricbeat"]
 [IMPORTANT]

metricbeat/docs/running-on-kubernetes.asciidoc

@@ -172,19 +172,12 @@ don't run this command, the default node selector will skip master nodes.
 [float]
 ==== Load {kib} dashboards
 
-{beatname_uc} comes packaged with example {kib} dashboards,
-visualizations, and searches for visualizing {beatname_uc} data in {kib}.
+{beatname_uc} comes packaged with various pre-built {kib} dashboards
+that you can use to visualize metrics about your Kubernetes environment.
 
-
-Before you can use the dashboards, you need to create the index pattern,
-+{beatname_lc}-*+, and load the dashboards into {kib}. To do this, run the `setup`
-command to load the recommended {ref}/indices-templates.html[index template]
-for writing to {es} and to deploy the sample dashboards for visualizing the data in {kib}.
-For details, see <<load-kibana-dashboards>>.
-
-Otherwise, you can
-<<configuration-dashboards,configure dashboard loading>> in the
-+{beatname_lc}.yml+ config file.
+If these dashboards are not already loaded into {kib}, you must <<{beatname_lc}-installation-configuration,install {beatname_uc}>>
+on any system that can connect to the {stack}, and then run the `setup` command to load the dashboards. To learn how,
+see <<load-kibana-dashboards,Load {kib} dashboards>>.
 
 [IMPORTANT]
 =======================================