diff --git a/docs/en/infraops/infra-ui-intro.asciidoc b/docs/en/infraops/infra-ui-intro.asciidoc
index e171a4dbd..c58284c7d 100644
--- a/docs/en/infraops/infra-ui-intro.asciidoc
+++ b/docs/en/infraops/infra-ui-intro.asciidoc
@@ -8,6 +8,9 @@ After you have infrastructure monitoring <<install-infrastructure-monitoring,up
 and data is streaming to {es}, use the {infra-ui} UI in {kib} to monitor your
 infrastructure and identify problems in real time.
 
+For more information about working with the {infra-ui} UI, see the
+{kibana-ref}/xpack-infra.html[{kib} documentation].
+
 [float]
 === Monitor your hosts and containers
 
diff --git a/docs/en/infraops/installation.asciidoc b/docs/en/infraops/installation.asciidoc
index add0ba089..0a5300140 100644
--- a/docs/en/infraops/installation.asciidoc
+++ b/docs/en/infraops/installation.asciidoc
@@ -7,9 +7,8 @@ beta[]
 To get up and running with infrastructure monitoring, you need:
 
 * An Elasticsearch cluster and Kibana (version 6.5 or later) with a basic
-license. To learn how to get up and running quickly, see
-{stack-gs}/get-started-elastic-stack.html[Getting started with the
-{stack}].
+license. To learn how to get started quickly, see
+{stack-gs}/get-started-elastic-stack.html[Getting started with the {stack}].
 +
 [TIP]
 ==============
@@ -20,7 +19,14 @@ https://www.elastic.co/cloud/elasticsearch-service/signup[Try out the {es}
 Service for free].
 ==============
 
-* {beats} shippers installed on each system you want to monitor
+* {beats} shippers (version 6.5 or later) installed on each system you want to
+monitor
+
+You might also need to modify UI settings in {kib} to change default behaviors,
+such as the index pattern used to query the data, and the timestamp field used
+for sorting. For more information, see
+{kibana-ref}/infrastructure-ui-settings-kb.html[{infra-ui} UI Settings] and
+{kibana-ref}/logs-ui-settings-kb.html[{logs-ui} UI Settings].
 
 [float]
 [[install-beats-for-infra-UI]]
@@ -86,7 +92,7 @@ module]
 * {filebeat-ref}/add-kubernetes-metadata.html[{filebeat} `add_kubernetes_metadata` processor]
 
 [float]
-==== More about monitoring containers
+==== More about container monitoring
 
 If you're monitoring containers, you can use autodiscover to automatically apply
 configuration changes in response to changes in your containers. To learn how,
diff --git a/docs/en/infraops/logs-ui-intro.asciidoc b/docs/en/infraops/logs-ui-intro.asciidoc
index cdefede2e..e0032768f 100644
--- a/docs/en/infraops/logs-ui-intro.asciidoc
+++ b/docs/en/infraops/logs-ui-intro.asciidoc
@@ -13,5 +13,8 @@ logs in real time and see a historical view of your log data. The search bar in
 the log viewer supports {kibana-ref}/kuery-query.html[Kibana Query Language].
 You can enter ad hoc or structured queries.
 
+For more information about working with the {logs-ui} UI, see the
+{kibana-ref}/xpack-logs.html[{kib} documentation].
+
 [role="screenshot"]
 image::screenshot-logs-ui.jpg[]