edits

Author: paigecalvert

docs/vendor/custom-domains-using.md

@@ -6,10 +6,6 @@ For information about adding and managing custom domains with the Vendor API v3,
 
 For more information about custom domains, see [About Custom Domains](custom-domains).
 
-## Known Issue
-
-If you use a custom domain for the Replicated Enterprise Portal and any of your customers use link transformers such as Microsoft Defender Safe Links, then there is a known issue where legitimate URLs in emails generated by the Enterprise Portal can break due to rewrapping. To avoid this issue, request a "Do not rewrite the following URLs" exclusion policy for your custom Enterprise Portal domain.
-
 ## Add a Custom Domain in the Vendor Portal {#add-domain}
 
 To add and verify a custom domain:
@@ -19,7 +15,7 @@ To add and verify a custom domain:
 1. In the **Add custom domain** dropdown, select the target Replicated endpoint.
 
     :::note
-    There is a known issue when using a custom domain for the Enterprise Portal if any of your customers use link transformers such as Microsoft Defender Safe Links. See [Known Issue](#known-issue) above.
+    There is a known issue when using a custom domain for the Enterprise Portal if any of your customers use link transformers such as Microsoft Defender Safe Links. For more information, see [Known Issue](custom-domains-using#known-issue) in _About Custom Domains_.
     :::
 
     The **Configure a custom domain** wizard opens.

docs/vendor/custom-domains.md

@@ -38,4 +38,8 @@ Using custom domains has the following limitations:
 
 - Each custom domain can only be used by one team.
 
-- For [Replicated Embedded Cluster](/vendor/embedded-overview) installations, any Helm [`extensions`](/reference/embedded-config) that you add in the Embedded Cluster Config do not use custom domains. During deployment, Embedded Cluster pulls both the repo for the given chart and any images in the chart as written. Embedded Cluster does not rewrite image names to use custom domains.
+- For [Replicated Embedded Cluster](/vendor/embedded-overview) installations, any Helm [`extensions`](/reference/embedded-config) that you add in the Embedded Cluster Config do not use custom domains. During deployment, Embedded Cluster pulls both the repo for the given chart and any images in the chart as written. Embedded Cluster does not rewrite image names to use custom domains.
+
+## Known Issue
+
+If you use a custom domain for the Replicated [Enterprise Portal](/vendor/enterprise-portal-about) and any of your customers use link transformers such as Microsoft Defender Safe Links, then there is a known issue where legitimate URLs in emails generated by the Enterprise Portal can break due to rewrapping. To avoid this issue, request a "Do not rewrite the following URLs" exclusion policy for your custom Enterprise Portal domain.

docs/vendor/enterprise-portal-about.mdx

@@ -39,6 +39,8 @@ For information about using the Enterprise Portal, see [Access and Use the Enter
 
 * Air gap instance records do not appear in the Enterprise Portal until the end customer creates an air gap instance record by either uploading a support bundle for that instance or manually entering instance information. For more information, see [View Active and Inactive Instances](/vendor/enterprise-portal-use#view-active-and-inactive-instances) in _Access and Use the Enterprise Portal_.
 
+* There is a known issue when using a custom domain for the Enterprise Portal if any of your customers use link transformers such as Microsoft Defender Safe Links. For more information, see [Known Issue](custom-domains-using#known-issue) in _About Custom Domains_. 
+
 ## Comparison to the Download Portal
 
 The Enterprise Portal is the next generation version of the Replicated Download Portal. Compared to the Download Portal, the Enterprise Portal not only provides access to installation assets and instructions, but also allows users to track available updates, manage their team and service accounts, view the status of their instances, view license details, and more. These features are designed to make it easier for your customers to manage their instances of your application from a centralized location outside of the installation environment.