edits

Author: paigecalvert

docs/enterprise/image-registry-settings.mdx

@@ -14,10 +14,12 @@ In online (internet-connected) KOTS installations, you can optionally use a loca
 
 To configure private registry settings in an online cluster:
 
-1. In the Admin Console, on the **Registry Settings** tab, edit the fields:
+1. In the Admin Console, on the **Registry settings** tab, edit the fields:
 
     <img src="/images/registry-settings.png" alt="Registry Settings" width="400"></img>
 
+    [View a larger version of this image](/images/registry-settings.png)
+
     The following table describes the fields:
 
     <ImageRegistrySettings/>
@@ -32,9 +34,11 @@ During air gap installations, you configure a private registry where KOTS pushes
 
 To change private registry settings in an air gap cluster:
 
-1. On the Registry Settings tab in the Admin Console, select the **Disable Pushing Images to Private Registry** checkbox, and click **Save changes**. 
+1. In the Admin Console, on the **Registry settings** tab, select the **Disable Pushing Images to Private Registry** checkbox. Click **Save changes**. 
 
-   This is a temporary action that allows you to edit the registry namespace and hostname. If you only want to change the username or password, you do not have to disable pushing the images.
+   :::note
+   This is a temporary action that allows you to edit the registry namespace and hostname. If you only want to change the username or password for the registry, you do not have to disable pushing the images.
+   :::
 
 1. Edit the fields as needed, and click **Save changes**.
 
@@ -61,15 +65,15 @@ To change private registry settings in an air gap cluster:
       </tr>
      </table>
 
-1. Deselect the **Disable Pushing Images to Private Registry** checkbox. This action re-enables KOTS to push images to your registry.
+1. Deselect the **Disable Pushing Images to Private Registry** checkbox. This action re-enables KOTS to push images to the registry.
 
 1. Click **Test Connection** to test the connection between KOTS and the private registry host.
 
 1. Click **Save changes**.
 
 ## Stop Using a Registry and Remove Registry Settings
 
-To stop using a registry:
+To stop using a registry and remove registry settings from the Admin Console:
 
 1. Log in to the Admin Console and go to **Registry Settings**.
 

docs/enterprise/installing-general-requirements.mdx

@@ -260,7 +260,7 @@ After manually creating these RBAC resources, the user must include both the `--
 
 A private image registry is required for air gap installations with KOTS in existing clusters. You provide the credentials for a compatible private registry during installation. You can also optionally configure a local private image registry for use with KOTS installations in online (internet-connected) environments.
 
-Private registry settings can be changed at any time. For more information, see [Using Private Registries](image-registry-settings).
+Private registry settings can be changed at any time. For more information, see [Configuring Local Image Registries for KOTS Installations](image-registry-settings).
 
 KOTS has been tested for compatibility with the following registries:
 

docs/reference/custom-resource-helmchart-v2.mdx

@@ -101,7 +101,7 @@ The `builder` key is required for the following use cases:
 
 * To support online installations that use a local private registry, the `builder` field renders the Helm chart with all of the necessary images so that KOTS knows where to pull the images.
 
-  You cannot prevent customers from configuring a local private registry in KOTS. If you think any of your customers will use a local private registry, you should use the `builder` key. For more information, see [Using Private Registries](/enterprise/image-registry-settings).
+  You cannot prevent customers from configuring a local private registry in KOTS. If you think any of your customers will use a local private registry, you should use the `builder` key. For more information, see [Configuring Local Image Registries for KOTS Installations](/enterprise/image-registry-settings).
 
 <HelmBuilderRequirements/>
 

docs/vendor/helm-native-v2-using.md

@@ -270,7 +270,7 @@ spec:
 
 ## Task 4: Support the Use of Local Image Registries {#local-registries}
 
-Local image registries are required for KOTS installations in air-gapped environments with no outbound internet connection. Also, users in online environments can optionally use a local registry. For more information about how users configure a local image registry with KOTS, see [Using Private Registries](/enterprise/image-registry-settings).
+Local image registries are required for KOTS installations in air-gapped environments with no outbound internet connection. Also, users in online environments can optionally use a local registry. For more information about how users configure a local image registry with KOTS, see [Configuring Local Image Registries for KOTS Installations](/enterprise/image-registry-settings).
 
 To support the use of local registries, configure the `builder` key. For more information about how to configure the `builder` key, see [`builder`](/reference/custom-resource-helmchart-v2#builder) in _HelmChart v2_.