Clean-up

Author: kilfoyle

docs/en/install-upgrade/air-gapped-install.asciidoc

@@ -37,11 +37,13 @@ Some components of the {stack} require additional configuration and local depend
 *** <<air-gapped-agent-integration-configure-yml>>
 *** <<air-gapped-agent-integration-configure-fleet-api>>
 
+NOTE: If you're working in an air-gapped environment and have a subscription level that includes Support coverage, link:https://www.elastic.co/contact[contact us] if you'd like to request an offline version of the Elastic documentation.
+
 [discrete]
 [[air-gapped-self-managed-linux]]
 === 1. Self-Managed Install (Linux)
 
-Refer to the section for each Elastic compopnent for air-gapped installation configuration and dependencies in a self-managed Linux environment.
+Refer to the section for each Elastic component for air-gapped installation configuration and dependencies in a self-managed Linux environment.
 
 [discrete]
 [[air-gapped-elasticsearch]]
@@ -55,14 +57,13 @@ Air-gapped install of {es} is fairly straightforward, as this component does not
 
 Air-gapped install of {kib} may require a number of additional services in the local network in order to access some of the features. General install and configuration guides are available in the {kibana-ref}/install.html[{kib} install documentation].
 
-Specifically (see appropriate sections in the rest of the doc):
+Specifically:
 
 * To be able to use {kib} mapping visualizations, you need to set up and configure the <<air-gapped-elastic-maps-service,Elastic Maps Service>>.
 * To be able to use {kib} sample data, install or update hundreds of prebuilt alert rules, and explore available data integrations, you need to set up and configure the <<air-gapped-elastic-package-registry,{package-registry}>>.
-To provide detection rule updates for {endpoint-sec} agents, you need to set up and configure the <<air-gapped-elastic-endpoint-artifact-repository,Elastic Endpoint Artifact Repository>>.
-To access {ents} capabilities (in addition to the general search capabilities of {es}), you need to set up and configure <<air-gapped-enterprise-search,{ents}>>.
-To access the APM integration, you need to set up and configure <<air-gapped-elastic-apm,Elastic APM>>. 
-
+* To provide detection rule updates for {endpoint-sec} agents, you need to set up and configure the <<air-gapped-elastic-endpoint-artifact-repository,Elastic Endpoint Artifact Repository>>.
+* To access {ents} capabilities (in addition to the general search capabilities of {es}), you need to set up and configure <<air-gapped-enterprise-search,{ents}>>.
+* To access the APM integration, you need to set up and configure <<air-gapped-elastic-apm,Elastic APM>>. 
 
 [discrete]
 [[air-gapped-beats]]
@@ -80,9 +81,9 @@ Elastic {beats} are light-weight data shippers. They do not require any unique s
 [[air-gapped-elastic-agent]]
 ==== 1.5. {agent}
 
-Air-gapped install of {agent} depends on the <<air-gapped-elastic-package-registry,{package-registry}>> and the <<air-gapped-elastic-artifact-registry,Elastic Artifact Registry>> for most use-cases. The agent itself is fairly lightweight and installs dependencies only as required by its configuration. In terms of connections to these dependencies, {agents} need to be able to connect to the Elastic Artifact Registry directly, but {package-registry} connections are handled through <<air-gapped-kibana,{kib}>>.
+Air-gapped install of {agent} depends on the <<air-gapped-elastic-package-registry,{package-registry}>> and the <<air-gapped-elastic-artifact-registry,{artifact-registry}>> for most use-cases. The agent itself is fairly lightweight and installs dependencies only as required by its configuration. In terms of connections to these dependencies, {agents} need to be able to connect to the {artifact-registry} directly, but {package-registry} connections are handled through <<air-gapped-kibana,{kib}>>.
 
-Additionally, if the {agent} {elastic-defend} integration is used, then <<air-gapped-elastic-endpoint-artifact-repository,Elastic Endpoint Artifact Repository>> is necessary in order to deploy updates for some of the detection and prevention capabilities.
+Additionally, if the {agent} {elastic-defend} integration is used, then access to the <<air-gapped-elastic-endpoint-artifact-repository,Elastic Endpoint Artifact Repository>> is necessary in order to deploy updates for some of the detection and prevention capabilities.
 
 To learn more about install and configuration, refer to the {fleet-guide}/elastic-agent-installation.html[{agent} install documentation].
 
@@ -93,7 +94,7 @@ To get a better understanding of how to work with {agent} configuration settings
 [[air-gapped-fleet]]
 ==== 1.6. {fleet-server}
 
-{fleet-server} is a required middleware component for any scalable deployment of the {agent}. Air-gapped dependencies of {fleet-server} are the same as those of the <<air-gapped-elastic-agent,{agent}>>.
+{fleet-server} is a required middleware component for any scalable deployment of the {agent}. The air-gapped dependencies of {fleet-server} are the same as those of the <<air-gapped-elastic-agent,{agent}>>.
 
 To learn more about installing {fleet-server}, refer to the {fleet-guide}/fleet-server.html[{fleet-server} set up documentation].
 
@@ -104,7 +105,7 @@ To learn more about installing {fleet-server}, refer to the {fleet-guide}/fleet-
 Air-gapped setup of the APM server is possible in two ways:
 
 * By setting up one of the {agent} deployments with an APM integration, as described in {apm-guide-ref}/apm-integration-upgrade-steps.html[Switch a self-installation to the APM integration].
-* Or, by installing a standalone Elastic APM Server, as described in the APM {apm-guide-ref}/configuring-howto-apm-server.html[configuration documentation].
+* Or, by installing a standalone Elastic APM Server, as described in the {apm-guide-ref}/configuring-howto-apm-server.html[APM configuration documentation].
 
 [discrete]
 [[air-gapped-elastic-maps-service]]
@@ -122,27 +123,27 @@ Detailed install and configuration instructions are available in the {enterprise
 [[air-gapped-elastic-package-registry]]
 ==== 1.10. {package-registry}
 
-Air-gapped install of the EPR is possible using any OCI-compatible runtime like Podman (a typical choice for RHEL-like Linux systems) or Docker. Links to the official container image and usage guide is available on the {fleet-ref}/air-gapped.html[Air-gapped environments] page in the {fleet} and {agent} Guide.
+Air-gapped install of the EPR is possible using any OCI-compatible runtime like Podman (a typical choice for RHEL-like Linux systems) or Docker. Links to the official container image and usage guide is available on the {fleet-guide}/air-gapped.html[Air-gapped environments] page in the {fleet} and {agent} Guide.
 
 Refer to <<air-gapped-elastic-package-registry-example>> for additional setup examples.
 
 NOTE: Besides setting up the EPR service, you also need to <<air-gapped-kibana,configure {kib}>> to use this service. If using TLS with the EPR service, it is also necessary to set up {kib} to trust the certificate presented by the EPR.
 
 [discrete]
 [[air-gapped-elastic-artifact-registry]]
-==== 1.11. Elastic Artifact Registry
+==== 1.11. {artifact-registry}
 
-Air-gapped install of the Elastic artifact registry is necessary in order to enable {agent} deployments to perform self-upgrades and install certain components which are needed for some of the data integrations (that is, in addition to what is also retrieved from the EPR). To learn how to set up such a repository, refer to {fleet-guide}/air-gapped.html#host-artifact-registry[Host your own artifact registry for binary downloads] in the {fleet} and {elastic-agent} Guide.
+Air-gapped install of the {artifact-registry} is necessary in order to enable {agent} deployments to perform self-upgrades and install certain components which are needed for some of the data integrations (that is, in addition to what is also retrieved from the EPR). To learn more, refer to {fleet-guide}/air-gapped.html#host-artifact-registry[Host your own artifact registry for binary downloads] in the {fleet} and {elastic-agent} Guide.
 
 Refer to <<air-gapped-elastic-artifact-registry-example>> for additional setup examples.
 
-NOTE: When setting up own web server, such as NGINX, to function as the Elastic Artifact Registry, it is recommended not to use TLS as there are, currently, no direct ways to establish certificate trust between {agents} and this service.
+NOTE: When setting up own web server, such as NGINX, to function as the {artifact-registry}, it is recommended not to use TLS as there are, currently, no direct ways to establish certificate trust between {agents} and this service.
 
 [discrete]
 [[air-gapped-elastic-endpoint-artifact-repository]]
 ==== 1.12. Elastic Endpoint Artifact Repository
 
-Air-gapped setup of this component is, essentially, identical to the setup of the <<air-gapped-elastic-artifact-registry,Elastic Artifact Registry>> except that different artifacts are served. To learn more, refer to {security-guide}/offline-endpoint.html[Configure offline endpoints and air-gapped environments] in the Elastic Security guide.
+Air-gapped setup of this component is, essentially, identical to the setup of the <<air-gapped-elastic-artifact-registry,{artifact-registry}>> except that different artifacts are served. To learn more, refer to {security-guide}/offline-endpoint.html[Configure offline endpoints and air-gapped environments] in the Elastic Security guide.
 
 [discrete]
 [[air-gapped-kubernetes-and-openshift]]
@@ -161,7 +162,7 @@ The main requirements are:
 * Syncing container images for ECK and all other {stack} components over to a locally-accessible container repository.
 * Modifying the ECK helm chart configuration so that ECK is aware that it is supposed to use your offline container repository instead of the public Elastic repository.
 * Optionally, disabling ECK telemetry collection in the ECK helm chart. This configuration propagates to all other Elastic components, such as {kib}.
-* Building your custom deployment container image for the Elastic Artifact Registry.
+* Building your custom deployment container image for the {artifact-registry}.
 * Building your custom deployment container image for the Elastic Endpoint Artifact Repository.
 
 [discrete]
@@ -174,15 +175,15 @@ This container would, ideally, run as a Kubernetes deployment. Refer to <<air-ga
 
 [discrete]
 [[air-gapped-k8s-os-elastic-artifact-registry]]
-==== 2.3. Elastic Artifact Registry
+==== 2.3. {artifact-registry}
 
 A custom container would need to be created following similar instructions to setting up a web server in the <<air-gapped-elastic-artifact-registry,self-managed install case>>. For example, a container file using an NGINX base image could be used to run a build similar to the example described in <<air-gapped-elastic-artifact-registry-example>>.
 
 [discrete]
 [[air-gapped-k8s-os-elastic-endpoint-artifact-repository]]
 ==== 2.4. Elastic Endpoint Artifact Repository
 
-Just like Elastic Artifact Registry. A custom container would need to be created following similar instructions to setting up a web server for the <<air-gapped-elastic-artifact-registry,self-managed install case>>.
+Just like the {artifact-registry}. A custom container needs to be created following similar instructions to setting up a web server for the <<air-gapped-elastic-artifact-registry,self-managed install case>>.
 
 [discrete]
 [[air-gapped-k8s-os-ironbank-secure-images]]
@@ -265,7 +266,7 @@ WantedBy=default.target
 
 [discrete]
 [[air-gapped-elastic-artifact-registry-example]]
-=== Appendix B - Elastic Artifact Registry
+=== Appendix B - {artifact-registry}
 
 The following example script downloads artifacts from the internet to be later served as a private Elastic Package Registry.
 
@@ -337,7 +338,7 @@ done
 
 ----
 
-The following is an example NGINX configuration for running a web server for the Elastic Artifact Registry.
+The following is an example NGINX configuration for running a web server for the {artifact-registry}.
 
 [source,shell]
 ----
@@ -454,7 +455,7 @@ When configuring any integration in {agent}, you need to set up integration sett
 Note the following terms and definitions:
 
 Integration::
-A variety of optional capabilities that can be deployed on top of the {stack}. refer to link:https://www.elastic.co/integrations/[Integrations] to learn more.
+A variety of optional capabilities that can be deployed on top of the {stack}. Refer to link:https://www.elastic.co/integrations/[Integrations] to learn more.
 
 Agent integration::
 The integrations that require {agent} to run. For example, the Sample Data integration requires only {es} and {kib} and consists of dashboards, data, and related objects, but the APM integration not only has some {es} objects, but also needs {agent} to run the APM Server.
@@ -483,7 +484,7 @@ There are three ways to configure {agent} integrations:
 
 *Example:* {observability-guide}/logs-metrics-get-started.html[Get started with logs and metrics]
 
-Agent policies and integration settings can be managed using the {kib} UI. For example, the following shows the configuration of logging for the System integration in an agent policy:
+Agent policies and integration settings can be managed using the {kib} UI. For example, the following shows the configuration of logging for the System integration in an {agent} policy:
 
 [role="screenshot"]
 image::images/air-gapped-configure-logging.png[Configuration of a logging integration in an agent policy]
@@ -498,10 +499,10 @@ image::images/air-gapped-configure-logging.png[Configuration of a logging integr
 
 NOTE: This documentation is still under development; there may be gaps around building custom agent policies.
 
-It is possible to have kibana create agent policies on your behalf by adding appropriate config items in `kibana.yml` settings file, these include:
+You can have {kib} create {agent} policies on your behalf by adding appropriate configuration parameters in the `kibana.yml` settings file, these include:
 
 `xpack.fleet.packages`::
-Takes a list of all integration package names and versions that {kib} should download from the {package-registry} (EPR). This is done because agents themselves do not directly fetch packages from the EPR.
+Takes a list of all integration package names and versions that {kib} should download from the {package-registry} (EPR). This is done because {agents} themselves do not directly fetch packages from the EPR.
 
 `xpack.fleet.agentPolicies`::
 Takes a list of {agent} policies in the format expected by the {fleet-guide}/fleet-api-docs.html[{kib} {fleet} HTTP API]. Refer to the setting in {kibana-ref}/fleet-settings-kb.html#_preconfiguration_settings_for_advanced_use_cases[Preconfiguration settings] for the format. See also <<air-gapped-agent-integration-configure-fleet-api>>.
@@ -518,7 +519,7 @@ You can add other, more discretionary settings for {fleet}, {agents}, & policies
 
 *Best option for*: Declarative configuration and users who need reproducible and automated deployments in even the trickiest of environments.
 
-*Example:* Read the following.
+*Example:* See the following.
 
 It is possible to use custom scripts that call the {kib} {fleet} API to create or update policies without restarting {kib}, and also allowing for custom error handling and update logic.