fixing broken bookmark

paulth1 · paulth1 · commit d3d14b679e52 · 2024-04-03T12:41:57.000-07:00
diff --git a/articles/frontdoor/domain.md b/articles/frontdoor/domain.md
@@ -165,7 +165,7 @@ After you've imported your certificate to a key vault, create an Azure Front Doo
 
 Then, configure your domain to use the Azure Front Door secret for its TLS certificate.
 
-For a guided walkthrough of these steps, see [Configure HTTPS on an Azure Front Door custom domain using the Azure portal](standard-premium/how-to-configure-https-custom-domain.md#using-your-own-certificate).
+For a guided walkthrough of these steps, see [Configure HTTPS on an Azure Front Door custom domain using the Azure portal](standard-premium/how-to-configure-https-custom-domain.md#use-your-own-certificate).
 
 ### Switch between certificate types
 
diff --git a/articles/frontdoor/front-door-how-to-onboard-apex-domain.md b/articles/frontdoor/front-door-how-to-onboard-apex-domain.md
@@ -91,7 +91,7 @@ You can use the Azure portal to onboard an apex domain on your Azure Front Door
 
 > [!NOTE]
 > * The **DNS state** column is used for CNAME mapping check. An apex domain doesn't support a CNAME record, so the DNS state shows **CNAME record is currently not detected** even after you add the alias record to the DNS provider.
-> * When placing a service like an Azure Web App behind Azure Front Door, you need to configure the web app with the same domain name as the root domain in Azure Front Door. You also need to configure the back-end host header with that domain name to prevent a redirect loop.
+> * When you place a service like an Azure Web App behind Azure Front Door, you need to configure the web app with the same domain name as the root domain in Azure Front Door. You also need to configure the back-end host header with that domain name to prevent a redirect loop.
 > * Apex domains don't have CNAME records pointing to the Azure Front Door profile. Managed certificate autorotation always fails unless domain validation is finished between rotations.
 
 ## Enable HTTPS on your custom domain
diff --git a/articles/frontdoor/standard-premium/how-to-add-custom-domain.md b/articles/frontdoor/standard-premium/how-to-add-custom-domain.md
@@ -37,7 +37,7 @@ A custom domain is configured on the **Domains** pane of the Azure Front Door pr
 
 1. On the **Add a domain** pane, select the domain type. You can choose **Non-Azure validated domain** or **Azure pre-validated domain**.
 
-    * **Non-Azure validated domain** is a domain that requires ownership validation. When you select **Non-Azure validated domain**, the recommended DNS management option is to use Azure-managed DNS. You might also use your own DNS provider. If you choose an Azure-managed DNS, select an existing DNS zone. Then select an existing custom subdomain or create a new one. If you're using another DNS provider, manually enter the custom domain name. Then select **Add** to add your custom domain.
+    * **Non-Azure validated domain** is a domain that requires ownership validation. When you select **Non-Azure validated domain**, we recommend that you use the Azure-managed DNS option. You might also use your own DNS provider. If you choose an Azure-managed DNS, select an existing DNS zone. Then select an existing custom subdomain or create a new one. If you're using another DNS provider, manually enter the custom domain name. Then select **Add** to add your custom domain.
 
         :::image type="content" source="../media/how-to-add-custom-domain/add-domain-page.png" alt-text="Screenshot that shows the Add a domain pane.":::
 
@@ -55,7 +55,7 @@ A custom domain is configured on the **Domains** pane of the Azure Front Door pr
     :::image type="content" source="../media/how-to-add-custom-domain/validation-state-submitting.png" alt-text="Screenshot that shows the domain validation state as Submitting.":::
 
     > [!NOTE]
-    > * Starting September 2023, Azure Front Door supports BYOC-based domain ownership validation. Azure Front Door automatically approves the domain ownership if the Certificate Name (CN) or Subject Alternative Name (SAN) of the provided certificate matches the custom domain. When you select **Azure managed certificate**, the domain ownership continues to be validated via the DNS TXT record.
+    > * As of September 2023, Azure Front Door now supports BYOC-based domain ownership validation. Azure Front Door automatically approves the domain ownership if the Certificate Name (CN) or Subject Alternative Name (SAN) of the provided certificate matches the custom domain. When you select **Azure managed certificate**, the domain ownership continues to be validated via the DNS TXT record.
     > * For custom domains created before BYOC-based validation is supported and the domain validation status is anything but **Approved**, you need to trigger the auto-approval of the domain ownership validation by selecting **Validation State** > **Revalidate** in the portal. If you're using the command-line tool, you can trigger domain validation by sending an empty `PATCH` request to the domain API.
     > * An Azure prevalidated domain has a validation state of **Pending**. It automatically changes to **Approved** after a few minutes. After validation gets approved, skip to [Associate the custom domain to your Front Door endpoint](#associate-the-custom-domain-with-your-azure-front-door-endpoint) and finish the remaining steps.
 
diff --git a/articles/frontdoor/standard-premium/how-to-configure-https-custom-domain.md b/articles/frontdoor/standard-premium/how-to-configure-https-custom-domain.md
@@ -41,7 +41,7 @@ If you have your own domain, and the domain isn't already associated with [anoth
     | DNS management | Select **Azure managed DNS (Recommended)**. |
     | DNS zone | Select the Azure DNS zone that hosts the custom domain. |
     | Custom domain | Select an existing domain or add a new domain. |
-    | HTTPS | Select **AFD Managed (Recommended)**. |
+    | HTTPS | Select **AFD managed (Recommended)**. |
 
 1. Validate and associate the custom domain to an endpoint by following the steps to enable a [custom domain](how-to-add-custom-domain.md).
 
@@ -62,8 +62,8 @@ If you have your own domain, and the domain is associated with [another Azure se
     | Setting | Value |
     |--|--|
     | Domain type | Select **Azure pre-validated domain**. |
-    | Pre-validated custom domain | Select a custom domain name from the dropdown list of Azure services. |
-    | HTTPS | Select **Azure managed (Recommended)**. |
+    | Pre-validated custom domains | Select a custom domain name from the dropdown list of Azure services. |
+    | HTTPS | Select **Azure managed**. |
 
 1. Validate and associate the custom domain to an endpoint by following the steps to enable a [custom domain](how-to-add-custom-domain.md).
 
@@ -180,7 +180,7 @@ Azure Front Door can now access this key vault and the certificates it contains.
 
     :::image type="content" source="../media/how-to-configure-https-custom-domain/add-custom-domain-https.png" alt-text="Screenshot that shows the Add a custom domain pane with HTTPS.":::
 
-1. Follow the onscreen steps to validate the certificate. Then associate the newly created custom domain to an endpoint as outlined in [creating a custom domain](how-to-add-custom-domain.md).
+1. Follow the onscreen steps to validate the certificate. Then associate the newly created custom domain to an endpoint as outlined in [Configure a custom domain](how-to-add-custom-domain.md).
 
 ## Switch between certificate types
 
