Merge pull request #228078 from duongau/cdnfreshness

CDN freshness review (Batch 1)

Author: Court72

articles/cdn/cdn-features.md

@@ -2,11 +2,10 @@
 title: Compare Azure Content Delivery Network (CDN) product features
 description: Learn about the features that each Azure Content Delivery Network (CDN) product supports.
 services: cdn
-documentationcenter: ''
 author: duongau
 ms.service: azure-cdn
 ms.topic: overview
-ms.date: 11/15/2019
+ms.date: 02/21/2023
 ms.author: duau
 ms.custom: mvc
 
@@ -34,7 +33,7 @@ The following table compares the features available with each product.
 | Change optimization type | |**✓** | | |
 | Origin Port |All TCP ports |[Allowed origin ports](/previous-versions/azure/mt757337(v%3Dazure.100)#allowed-origin-ports) |All TCP ports |All TCP ports |
 | [Global server load balancing (GSLB)](../traffic-manager/traffic-manager-load-balancing-azure.md)  | **✓** |**✓** |**✓** |**✓** |
-| [Fast purge](cdn-purge-endpoint.md)  | **✓** |**✓**, Purge all and Wildcard purge are not supported by Azure CDN from Akamai currently |**✓** |**✓** |
+| [Fast purge](cdn-purge-endpoint.md)  | **✓** |**✓**, Purge all and Wildcard purge aren't supported by Azure CDN from Akamai currently |**✓** |**✓** |
 | [Asset pre-loading](cdn-preload-endpoint.md)  |  | |**✓** |**✓** |
 | Cache/header settings (using [caching rules](cdn-caching-rules.md))  |**✓** using [Standard rules engine](cdn-standard-rules-engine.md)  |**✓** |**✓** | |
 | Customizable, rules based content delivery engine |**✓** using [Standard rules engine](cdn-standard-rules-engine.md)  | | |**✓** using [rules engine](./cdn-verizon-premium-rules-engine.md) |

articles/cdn/cdn-map-content-to-custom-domain.md

@@ -3,12 +3,12 @@ title: 'Tutorial: Add a custom domain to your endpoint'
 titleSuffix: Azure Content Delivery Network
 description: Use this tutorial to add a custom domain to an Azure Content Delivery Network endpoint so that your domain name is visible in your URL.
 services: cdn
-author: jessie-jyy
+author: duongau
 manager: KumudD
 ms.service: azure-cdn
 ms.topic: tutorial
-ms.date: 04/12/2021
-ms.author: yuajia
+ms.date: 02/21/2023
+ms.author: duau
 ms.custom: mvc, devx-track-azurepowershell
 #Customer intent: As a website owner, I want to add a custom domain to my CDN endpoint so that my users can use my custom domain to access my content.
 ---
@@ -17,7 +17,7 @@ ms.custom: mvc, devx-track-azurepowershell
 
 This tutorial shows how to add a custom domain to an Azure Content Delivery Network (CDN) endpoint. 
 
-The endpoint name in your CDN profile is a subdomain of azureedge.net. By default when delivering content, the CDN profile domain is included within the URL.
+The endpoint name in your CDN profile is a subdomain of azureedge.net. By default when delivering content, the CDN profile domain gets included in the URL.
 
 For example, `https://contoso.azureedge.net/photo.png`.
 
@@ -55,16 +55,16 @@ For Azure CDN, the source domain name is your custom domain name and the destina
 
 Azure CDN routes traffic addressed to the source custom domain to the destination CDN endpoint hostname after it verifies the CNAME record.
 
-A custom domain and its subdomain can be added to only a single endpoint at a time. 
+A custom domain and its subdomain can only get added to a single endpoint at a time. 
 
 Use multiple CNAME records for different subdomains from the same custom domain for different Azure services.
 
 You can map a custom domain with different subdomains to the same CDN endpoint.
 
 > [!NOTE]
 > - This tutorial uses the CNAME record type for multiple purposes:
->   - *Traffic routing* can be accomplished with a CNAME record as well as A or AAAA record types in Azure DNS. To apply, follow the steps below and replace the CNAME record with the record type of your choice.  
->   - A CNAME record is **required** for custom domain *ownership validation* and must be available when adding the custom domain to a CDN Endpoint.  More details below.
+>   - *Traffic routing* can be accomplished with a CNAME record as well as A or AAAA record types in Azure DNS. To apply, use the following steps to replace the CNAME record with the record type of your choice.  
+>   - A CNAME record is **required** for custom domain *ownership validation* and must be available when adding the custom domain to a CDN Endpoint. More details in the following section.
 
 ---
 # [**Azure DNS**](#tab/azure-dns)
@@ -152,7 +152,7 @@ To create a CNAME record for your custom domain:
 
 3. Save your changes.
 
-4. If you're previously created a temporary cdnverify subdomain CNAME record, delete it. 
+4. If you previously created a temporary cdnverify subdomain CNAME record, delete it. 
 
 5. If you're using this custom domain in production for the first time, follow the steps for [Add the custom domain with your CDN endpoint](#add-a-custom-domain-to-your-cdn-endpoint) and [Verify the custom domain](#verify-the-custom-domain).
 
@@ -175,7 +175,7 @@ After you've registered your custom domain, you can then add it to your CDN endp
 
    :::image type="content" source="media/cdn-map-content-to-custom-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**, gets generated and pre-filled from your CDN endpoint URL: **\<endpoint-hostname>**.azureedge.net. You can't change this value.
 
 5. For **Custom hostname**, enter your custom domain, including the subdomain, to use as the source domain of your CNAME record. 
     1. For example, **www.contoso.com** or **cdn.contoso.com**. **Don't use the cdnverify subdomain name**.
@@ -184,7 +184,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 gets 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. 
@@ -218,7 +218,7 @@ After you've registered your custom domain, you can then add it to your CDN endp
     New-AzCdnCustomDomain @parameters
 ```
 
-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 gets validated. 
 
    It can take some time for the new custom domain settings to propagate to all CDN edge nodes: 
 
@@ -232,7 +232,7 @@ Azure verifies that the CNAME record exists for the custom domain name you enter
 
 After you've completed the registration of your custom domain, verify that the custom domain references your CDN endpoint.
 
-1. Ensure that you have public content that is cached at the endpoint. For example, if your CDN endpoint is associated with a storage account, Azure CDN will cache the content in a public container. Set your container to allow public access and it contains at least one file to test the custom domain.
+1. Ensure that you have public content that you want cached at the endpoint. For example, if your CDN endpoint is associated with a storage account, Azure CDN caches the content in a public container. Set your container to allow public access and it contains at least one file to test the custom domain.
 
 2. In your browser, navigate to the address of the file by using the custom domain. For example, if your custom domain is `www.contoso.com`, the URL to the cached file should be similar to the following URL: `http://www.contoso.com/my-public-container/my-file.jpg`. Verify that the result is that same as when you access the CDN endpoint directly at **\<endpoint-hostname>**.azureedge.net.
 
@@ -252,7 +252,7 @@ If you no longer want to associate your endpoint with a custom domain, remove th
 
 3. From the **Endpoint** page, under Custom domains, right-click the custom domain that you want to remove, then select **Delete** from the context menu. Select **Yes**.
 
-   The custom domain is removed from your endpoint.
+   The custom domain gets removed from your endpoint.
 
 # [**PowerShell**](#tab/azure-powershell-cleanup)
 

articles/cdn/cdn-overview.md

@@ -2,35 +2,32 @@
 title: What is a content delivery network (CDN)? - Azure | Microsoft Docs
 description: Learn what Azure Content Delivery Network (CDN) is and how to use it to deliver high-bandwidth content.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
+manager: kumud
 ms.assetid: 866e0c30-1f33-43a5-91f0-d22f033b16c6
 ms.service: azure-cdn
-ms.workload: tbd
-ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 05/09/2018
+ms.date: 02/21/2023
 ms.author: duau
 ms.custom: mvc
 
 ---
 # What is a content delivery network on Azure?
-A content delivery network (CDN) is a distributed network of servers that can efficiently deliver web content to users. CDNs store cached content on edge servers in point-of-presence (POP) locations that are close to end users, to minimize latency. 
 
-Azure Content Delivery Network (CDN) offers developers a global solution for rapidly delivering high-bandwidth content to users by caching their content at strategically placed physical nodes across the world. Azure CDN can also accelerate dynamic content, which cannot be cached, by leveraging various network optimizations using CDN POPs. For example, route optimization to bypass Border Gateway Protocol (BGP).
+A content delivery network (CDN) is a distributed network of servers that can efficiently deliver web content to users. A CDN store cached content on edge servers in point-of-presence (POP) locations that are close to end users, to minimize latency. 
+
+Azure CDN offers developers a global solution for rapidly delivering high-bandwidth content to users by caching their content at strategically placed physical nodes across the world. Azure CDN can also accelerate dynamic content, which can't get cached, by using various network optimizations using CDN POPs. For example, route optimization to bypass Border Gateway Protocol (BGP).
 
 The benefits of using Azure CDN to deliver web site assets include:
 
-* Better performance and improved user experience for end users, especially when using applications in which multiple round-trips are required to load content.
+* Better performance and improved user experience for end users, especially when using applications where multiple round-trips requests required by end users to load contents.
 * Large scaling to better handle instantaneous high loads, such as the start of a product launch event.
-* Distribution of user requests and serving of content directly from edge servers so that less traffic is sent to the origin server.
+* Distribution of user requests and serving of content directly from edge servers so that less traffic gets sent to the origin server.
 
 For a list of current CDN node locations, see [Azure CDN POP locations](cdn-pop-locations.md).
 
 ## How it works
+
 ![CDN Overview](./media/cdn-overview/cdn-overview.png)
 
 1. A user (Alice) requests a file (also called an asset) by using a URL with a special domain name, such as _<endpoint name>_.azureedge.net. This name can be an endpoint hostname or a custom domain. The DNS routes the request to the best performing POP location, which is usually the POP that is geographically closest to the user.
@@ -41,20 +38,21 @@ For a list of current CDN node locations, see [Azure CDN POP locations](cdn-pop-
 
 4. An edge server in the POP caches the file and returns the file to the original requestor (Alice). The file remains cached on the edge server in the POP until the time-to-live (TTL) specified by its HTTP headers expires. If the origin server didn't specify a TTL, the default TTL is seven days.
 
-5. Additional users can then request the same file by using the same URL that Alice used, and can also be directed to the same POP.
+5. More users can then request the same file by using the same URL that Alice used, and gets directed to the same POP.
 
 6. If the TTL for the file hasn't expired, the POP edge server returns the file directly from the cache. This process results in a faster, more responsive user experience.
 
 ## Requirements
 * To use Azure CDN, you must own at least one Azure subscription. 
 * You also need to create a CDN profile, which is a collection of CDN endpoints. Every CDN endpoint is a specific configuration which users can customize with required content delivery behavior and access. To organize your CDN endpoints by internet domain, web application, or some other criteria, you can use multiple profiles. 
-* Since [Azure CDN pricing](https://azure.microsoft.com/pricing/details/cdn/) is applied at the CDN profile level, you must create multiple CDN profiles if you want to use a mix of pricing tiers. For information about the Azure CDN billing structure, see [Understanding Azure CDN billing](cdn-billing.md).
+* Since [Azure CDN pricing](https://azure.microsoft.com/pricing/details/cdn/) gets applied at the CDN profile level, so if you want to use a mix of pricing tiers you must create multiple CDN profiles. For information about the Azure CDN billing structure, see [Understanding Azure CDN billing](cdn-billing.md).
 
 ### Limitations
+
 Each Azure subscription has default limits for the following resources:
- - The number of CDN profiles that can be created.
- - The number of endpoints that can be created in a CDN profile. 
- - The number of custom domains that can be mapped to an endpoint.
+ - The number of CDN profiles created.
+ - The number of endpoints created in a CDN profile. 
+ - The number of custom domains mapped to an endpoint.
 
 For more information about CDN subscription limits, see [CDN limits](../azure-resource-manager/management/azure-subscription-service-limits.md).