update links and add compatible registries partial

Author: paigecalvert

docs/enterprise/image-registry-settings.mdx

@@ -1,20 +1,21 @@
 import ImageRegistrySettings from "../partials/image-registry/_image-registry-settings.mdx"
+import DockerCompatibility from "../partials/image-registry/_docker-compatibility.mdx"
 
 # Configuring Local Image Registries
 
 This topic describes how to configure private registry settings in the Replicated KOTS Admin Console.
 
-The information in this topic applies to existing cluster installations with KOTS and installations with Replicated kURL.
+The information in this topic applies to existing cluster installations with KOTS and installations with Replicated kURL. This topic does _not_ apply to Replciated Embedded Cluster installations.
 
 ## Overview
 
-Using a private registry lets you create a custom image pipeline. Any proprietary configurations that you make to the application are shared only with the groups that you allow access, such as your team or organization. You also have control over the storage location, logging messages, load balancing requests, and other configuration options.
+Using a private registry lets you create a custom image pipeline. Any proprietary configurations that you make to the application are shared only with the groups that you allow access, such as your team or organization. You also have control over the storage location, logging messages, load balancing requests, and other configuration options. Private registries can be used with online or air gap clusters.
 
-Private registries can be used with online or air gap clusters.
+## Requirement
 
-## Prerequisite
+The domain of the image registry must support a Docker V2 protocol. KOTS has been tested for compatibility with the following registries:
 
-The domain of the image registry must support a Docker V2 protocol. For more information, see [Compatible Image Registries](installing-general-requirements#registries) in _KOTS Installation Requirements_.
+<DockerCompatibility/>
 
 ## Configure Local Private Registries in Online Clusters
 

docs/enterprise/installing-general-requirements.mdx

@@ -258,9 +258,9 @@ After manually creating these RBAC resources, the user must include both the `--
 
 ## Compatible Image Registries {#registries}
 
-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.
+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 installations in online (internet-connected) environments.
 
-Private registry settings can be changed at any time. For more information, see [Configuring Local Image Registries for KOTS Installations](image-registry-settings).
+Private registry settings can be changed at any time. For more information, see [Configuring Local Image Registries](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 [Configuring Local Image Registries for KOTS Installations](/enterprise/image-registry-settings).
+  You cannot prevent customers from configuring a local private registry in the Admin Console. 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](/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 [Configuring Local Image Registries for KOTS Installations](/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](/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_.