update title and xrefs

Author: paigecalvert

docs/enterprise/installing-existing-cluster-automation.mdx

@@ -13,15 +13,15 @@ import PushKotsImages from "../partials/install/_push-kotsadm-images.mdx"
 import KotsVersionMatch from "../partials/install/_kots-airgap-version-match.mdx"
 import PlaceholderRoCreds from "../partials/install/_placeholder-ro-creds.mdx"
 
-# Installing with the CLI
+# Installing from the Command Line
 
 This topic describes how to install an application with Replicated KOTS, Replicated Embedded Cluster, or Replicated kURL from the command line.
 
 ## Overview
 
-You can use the command line to install an application with Replicated KOTS, Replicated Embedded Cluster, or Replicated kURL. A common use case for installing with the CLI is to automate installation, such as performing headless installations as part of CI/CD pipelines.
+You can use the command line to install an application with Replicated KOTS, Replicated Embedded Cluster, or Replicated kURL. A common use case for installing from the command line is to automate installation, such as performing headless installations as part of CI/CD pipelines.
 
-To install with the CLI, you provide all the necessary installation assets, such as the license file and the application config values, with the installation command rather than through the Admin Console UI. Any preflight checks defined for the application run automatically during CLI installations rather than being displayed in the Admin Console.
+To install from the command line, you provide all the necessary installation assets, such as the license file and the application config values, with the installation command rather than through the Admin Console UI. Any preflight checks defined for the application run automatically during headless installations from the command line rather than being displayed in the Admin Console.
 
 ## Prerequisite
 

docs/enterprise/installing-overview.md

@@ -48,7 +48,7 @@ For information about image registry requirements, see [Private Registry Require
 
 You can automate application installation in online, air gap, existing cluster, and embedded cluster environments using the KOTS CLI. In an automated installation, you provide all the information required to install and deploy the application with the `kots install` command, rather than providing this information in the Replicated Admin Console.
 
-For more information, see [Installing with Automation](/enterprise/installing-existing-cluster-automation).
+For more information, see [Installing from the Command Line](/enterprise/installing-existing-cluster-automation).
 
 ### KOTS Installations Without Object Storage
 

docs/intro-kots.md

@@ -70,4 +70,4 @@ The kots command-line interface (CLI) is a kubectl plugin. Customers can run com
 
 For information about getting started with the KOTS CLI, see [Installing the KOTS CLI](/reference/kots-cli-getting-started).
 
-The KOTS CLI can also be used to install an application without needing to access the Admin Console. This can be useful for automating installations and upgrades. For information about how to run automated installations with the KOTS CLI, see [Installing with the CLI](/enterprise/installing-existing-cluster-automation).
+The KOTS CLI can also be used to install an application without needing to access the Admin Console. This can be useful for automating installations and upgrades, such as in CI/CD pipelines. For information about how to perform headless installations from the command line, see [Installing from the Command Line](/enterprise/installing-existing-cluster-automation).

docs/reference/kots-cli-install.mdx

@@ -57,7 +57,7 @@ This command supports all [global flags](kots-cli-global-flags) and also:
     <tr>
         <td><code>--config-values</code></td>
         <td>string</td>
-        <td>Path to a manifest file containing configuration values. This manifest must be <code>apiVersion: kots.io/v1beta1</code> and <code>kind: ConfigValues</code>. For more information, see <a href="/enterprise/installing-existing-cluster-automation">Installing with the CLI</a>.</td>
+        <td>Path to a manifest file containing configuration values. This manifest must be <code>apiVersion: kots.io/v1beta1</code> and <code>kind: ConfigValues</code>. For more information, see <a href="/enterprise/installing-existing-cluster-automation">Installing from the Command Line</a>.</td>
     </tr>
     <tr>
         <td><code>--copy-proxy-env</code></td>

docs/vendor/embedded-overview.mdx

@@ -55,7 +55,7 @@ Embedded Cluster has the following limitations:
 
 * **Changing node hostnames is not supported**: After a host is added to a Kubernetes cluster, Kubernetes assumes that the hostname and IP address of the host will not change. If you need to change the hostname or IP address of a node, you must first remove the node from the cluster. For more information about the requirements for naming nodes, see [Node name uniqueness](https://kubernetes.io/docs/concepts/architecture/nodes/#node-name-uniqueness) in the Kubernetes documentation.
 
-* **Automated installations not supported**: Users cannot do automated (headless) Embedded Cluster installations because it is not possible to configure the application by passing the [ConfigValues](/vendor/releases-configvalues) file with the installation command. Embedded Cluster installations require that the application is configured from the Admin Console config screen. For more information about automating existing cluster or kURL installations with the KOTS CLI, see [Installing with the CLI](/enterprise/installing-existing-cluster-automation).
+* **Automated installations not supported**: Users cannot do automated (headless) Embedded Cluster installations because it is not possible to configure the application by passing the [ConfigValues](/vendor/releases-configvalues) file with the installation command. Embedded Cluster installations require that the application is configured from the Admin Console config screen. For more information about automating existing cluster or kURL installations with the KOTS CLI, see [Installing from the Command Line](/enterprise/installing-existing-cluster-automation).
 
 * **Automatic updates not supported**: Configuring automatic updates from the Admin Console so that new versions are automatically deployed is not supported for Embedded Cluster installations. For more information, see [Configuring Automatic Updates](/enterprise/updating-apps).
 

docs/vendor/packaging-rbac.md

@@ -108,7 +108,7 @@ The following limitations apply when using the `requireMinimalRBACPrivileges` or
 
    In non-headless installations in air gap environments, KOTS does not have access to the application's `.airgap` package during installation. This means that KOTS does not have the information required to determine whether namespace-scoped access is needed, so it defaults to the more permissive, default cluster-scoped RBAC policy.
 
-   For more information about how to do headless installations in air gap environments, see [Air Gap Existing Cluster](/enterprise/installing-existing-cluster-automation#air-gap-existing-cluster) in _Installing with the CLI_.
+   For more information about how to do headless installations in air gap environments, see [Air Gap Install](/enterprise/installing-existing-cluster-automation#air-gap-install) in _Installing from the Command Line_.
 
 * **Changing RBAC permissions for installed instances**: The RBAC permissions for KOTS are set during its initial installation. KOTS runs using the assumed identity and cannot change its own authorization. When you update your application to add or remove the `requireMinimalRBACPrivileges` and `supportMinimalRBACPrivileges` flags in the Application custom resource, the RBAC permissions for KOTS are affected only for new installations. Existing KOTS installations continue to run with their current RBAC permissions.
 

docs/vendor/releases-configvalues.md

@@ -18,7 +18,7 @@ The KOTS ConfigValues file includes the fields that are defined in the KOTS Conf
 
 The ConfigValues file allows you to pass the configuration values for an application from the command line with the install command, rather than through the Admin Console UI. This supports automated or _headless_ installations, such as when installing an application as part of CI/CD pipelines. 
 
-For more information about installing from the command line, see [Installing with the CLI](/enterprise/installing-existing-cluster-automation).
+For more information about installing from the command line, see [Installing from the Command Line](/enterprise/installing-existing-cluster-automation).
 
 ## Get the ConfigValues File
 

docs/vendor/replicated-sdk-airgap.mdx

@@ -39,9 +39,4 @@ Replicated does not provide air gap bundles for applications installed with the
 
 ### KOTS
 
-When the SDK is installed by KOTS in an air gap environment, KOTS automatically sets `isAirGap: true` in the SDK Helm chart values to enable air gap mode. No additional configuration is required.
-
-KOTS automatically enables air gap mode for the SDK when the user follows any of these procedures to do an air gap installation:
-* [Air Gap Installation in Existing Clusters](/enterprise/installing-existing-cluster-airgapped)
-* [Air Gap Installation with kURL](/enterprise/installing-kurl-airgap)
-* [Air Gap Existing Cluster](/enterprise/installing-existing-cluster-automation#air-gap-existing-cluster) or [Air Gap kURL Cluster](/enterprise/installing-existing-cluster-automation#air-gap-kurl-cluster) in _Installing with the CLI_
+When the SDK is installed by KOTS in an air gap environment, KOTS automatically sets `isAirGap: true` in the SDK Helm chart values to enable air gap mode. No additional configuration is required.

docs/vendor/replicated-sdk-customizing.md

@@ -117,7 +117,7 @@ replicated:
 ```
 
 :::note
-If the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` variables are configured with the [kots install](/enterprise/installing-existing-cluster-automation) command, these variables will also be set automatically in the Replicated SDK.
+If the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` variables are configured with the [kots install](/reference/kots-cli-install) command, these variables will also be set automatically in the Replicated SDK.
 :::
 
 **Example**:
@@ -152,7 +152,7 @@ To use a CA stored in a ConfigMap:
    ```
 
 :::note
-If the `--private-ca-configmap` flag is used with the [kots install](/enterprise/installing-existing-cluster-automation) command, this value will be populated in the Replicated SDK automatically.
+If the `--private-ca-configmap` flag is used with the [kots install](/reference/kots-cli-install) command, this value will be populated in the Replicated SDK automatically.
 :::
 
 ### Using a Secret

sidebars.js

@@ -369,7 +369,7 @@ const sidebars = {
               },
               {
                 type: 'category',
-                label: 'Installing with the CLI',
+                label: 'Installing from the Command Line',
                 items: [
                   'enterprise/installing-existing-cluster-automation',
                   'vendor/releases-configvalues',