freshness review

Author: duongau

articles/cdn/onboard-apex-domain.md

@@ -5,7 +5,7 @@ services: cdn
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 11/07/2020
+ms.date: 02/27/2023
 ms.author: duau
 
 ---
@@ -17,7 +17,7 @@ The DNS protocol prevents the assignment of CNAME records at the zone apex. For
 
 This problem can be resolved by using alias records in Azure DNS. Unlike CNAME records, alias records are created at the zone apex. Application owners can use it to point their zone apex record to a CDN profile that has public endpoints. Application owners point to the same CDN profile that's used for any other domain within their DNS zone. For example, `contoso.com` and `www.contoso.com` can point to the same CDN profile. 
 
-Mapping your apex or root domain to your CDN profile requires CNAME flattening or DNS chasing. A mechanism where the DNS provider recursively resolves the CNAME entry until it hits an IP address. This functionality is supported by Azure DNS for CDN endpoints. 
+Mapping your apex or root domain to your CDN profile requires CNAME flattening or DNS chasing. A mechanism where the DNS provider recursively resolves the CNAME entry until it hits an IP address. This functionality is supported with Azure DNS for CDN endpoints. 
 
 > [!NOTE]
 > There are other DNS providers as well that support CNAME flattening or DNS chasing, however, Azure CDN recommends using Azure DNS for its customers for hosting their domains.
@@ -47,7 +47,7 @@ You can use the Azure portal to onboard an apex domain on your CDN and enable HT
 
     :::image type="content" source="./media/onboard-apex-domain/cdn-apex-alias-record.png" alt-text="Alias record for zone apex":::
 
-6. The above step will create a zone apex record pointing to your CDN resource. A CNAME record-mapping **cdnverify** is used for onboarding the domain on your CDN profile.
+6. The above step creates a zone apex record pointing to your CDN resource. A CNAME record-mapping **cdnverify** is used for onboarding the domain on your CDN profile.
     1. Example, **cdnverify.contoso.com**.
 
 
@@ -65,7 +65,7 @@ After you've registered your custom domain, you can then add it to your CDN endp
 
    :::image type="content" source="media/onboard-apex-domain/cdn-custom-domain-button.png" alt-text="Add custom domain button" border="true":::
 
-4. In **Add a custom domain**, **Endpoint hostname**, is pre-filled and is derived from your CDN endpoint URL: **\<endpoint-hostname>**.azureedge.net. It cannot be changed.
+4. In **Add a custom domain**, **Endpoint hostname**, is pre-filled and is derived from your CDN endpoint URL: **\<endpoint-hostname>**.azureedge.net. It can't be changed.
 
 5. For **Custom hostname**, enter your custom root or apex domain to use as the source domain of your CNAME record. 
     1. For example, **contoso.com**. **Don't use the cdnverify subdomain name**.
@@ -74,7 +74,7 @@ After you've registered your custom domain, you can then add it to your CDN endp
 
 6. Select **Add**.
 
-   Azure verifies that the CNAME record exists for the custom domain name you entered. If the CNAME is correct, your custom domain will be validated. 
+   Azure verifies that the CNAME record exists for the custom domain name you entered. If the CNAME is correct, your custom domain is validated. 
 
    It can take some time for the new custom domain settings to propagate to all CDN edge nodes: 
     - For **Azure CDN Standard from Microsoft** profiles, propagation usually completes in 10 minutes.