edits

Author: paigecalvert

docs/enterprise/installing-embedded-automation.mdx

@@ -14,7 +14,7 @@ With headless installation, you provide all the necessary installation assets, s
 
 ## Prerequisite
 
-Create a Replicated KOTS ConfigValues resource to define the configuration values for the application. The ConfigValues resource 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. For air-gapped environments, ensure that the ConfigValues file can be accessed from the installation environment. 
+Create a ConfigValues resource to define the configuration values for the application. The ConfigValues resource 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. For air-gapped environments, ensure that the ConfigValues file can be accessed from the installation environment. 
 
 The ConfigValues resource includes the fields that are defined in the Replicated KOTS Config custom resource for the release, along with the user-supplied and default values for each field, as shown in the example below:
 

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

@@ -1,5 +1,5 @@
 import ConfigValuesExample from "../partials/configValues/_configValuesExample.mdx"
-import ConfigValuesProcedure from "../partials/configValues/_config-values-procedure.mdx"
+import ConfigValuesRequirements from "../partials/configValues/_requirements.mdx"
 import PlaceholdersGlobal from "../partials/install/_placeholders-global.mdx"
 import PlaceholderAirgapBundle from "../partials/install/_placeholder-airgap-bundle.mdx"
 import PlaceholderNamespaceExisting from "../partials/install/_placeholder-namespace-existing.mdx"
@@ -39,13 +39,17 @@ The following shows an example of the output from the kots install command:
 
 ## Prerequisite
 
-Create a ConfigValues YAML file to define the configuration values for the application release. 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. For air-gapped environments, ensure that the ConfigValues file can be accessed from the installation environment. 
+Create a ConfigValues resource to define the configuration values for the application. The ConfigValues resource 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. For air-gapped environments, ensure that the ConfigValues file can be accessed from the installation environment. 
 
-The KOTS ConfigValues file includes the fields that are defined in the KOTS Config custom resource for an application release, along with the user-supplied and default values for each field, as shown in the example below:
+The ConfigValues resource includes the fields that are defined in the Replicated KOTS Config custom resource for the release, along with the user-supplied and default values for each field, as shown in the example below:
 
 <ConfigValuesExample/>
 
-<ConfigValuesProcedure/>
+#### ConfigValues Requirements
+
+<ConfigValuesRequirements/>
+
+For more information, see [ConfigValues](/reference/custom-resource-configvalues).
 
 ## Online (Internet-Connected) Installation
 

docs/reference/custom-resource-configvalues.mdx

@@ -1,5 +1,6 @@
 import ConfigValuesExample from "../partials/configValues/_configValuesExample.mdx"
 import ConfigValuesRequirements from "../partials/configValues/_requirements.mdx"
+import GetConfigValues from "../partials/configValues/_config-values-procedure.mdx"
 
 # ConfigValues
 
@@ -13,7 +14,7 @@ The ConfigValues resource lists the values and defaults for each application con
 
 In automated or headless installations, end users provide a ConfigValues resource with the install command to set the application configuration values from the command line rather than through the Admin Console UI. For more information about performing headless installations with Replicated Embedded Cluster, see [Automate Embedded Cluster Installations](/enterprise/installing-embedded-automation). For information about performing headless installations with KOTS in an existing cluster, see [Install with the KOTS CLI](/enterprise/installing-existing-cluster-automation).
 
-Additionally, for each installation, the Admin Console automatically generates a ConfigValues resource and makes it available for download in the Admin Console **View files** tab.
+Additionally, for each installation, the Admin Console automatically generates a ConfigValues resource and makes it available for download in the Admin Console **View files** tab or with the [`kots get config`](/reference/kots-cli-get-config) command. For more information, see [Download the ConfigValues for an Installation](#download) below.
 
 The following image shows how application configuration items defined a Config resource map to a ConfigValues resource:
 
@@ -116,4 +117,10 @@ spec:
       valuePlainText: exampleclientsecret
     slack_user_token:
       valuePlainText: exampleusertoken
-```
+```
+
+## Download the ConfigValues for an Installation {#download}
+
+For each installation, the Admin Console automatically generates a ConfigValues resource and makes it available for download in the Admin Console **View files** tab or with the [`kots get config`](/reference/kots-cli-get-config) command.
+
+<GetConfigValues/>