Merge pull request #228818 from duongau/cdnfreshness5

CDN freshness review (Batch 5)

Author: JamesJBarnett

articles/cdn/cdn-create-endpoint-how-to.md

@@ -2,28 +2,28 @@
 title: Create an Azure CDN endpoint | Microsoft Docs
 description: This article shows how to create a new Azure Content Delivery Network (CDN) endpoint, including advanced settings.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
+manager: kumudd
 ms.service: azure-cdn
 ms.workload: media
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 09/09/2021
+ms.date: 02/27/2023
 ms.author: duau
 ms.custom: mvc
-
 ---
+
 # Create an Azure CDN endpoint
+
 This article describes all the settings for creating an [Azure Content Delivery Network (CDN)](cdn-overview.md) endpoint in an existing CDN profile. After you've created a profile and an endpoint, you can start delivering content to your customers. For a quickstart on creating a profile and endpoint, see [Quickstart: Create an Azure CDN profile and endpoint](cdn-create-new-endpoint.md).
 
 ## Prerequisites
+
 Before you can create a CDN endpoint, you must have created at least one CDN profile, which can contain one or more CDN endpoints. To organize your CDN endpoints by internet domain, web application, or some other criteria, you can use multiple profiles. Because CDN pricing is applied at the CDN profile level, you must create multiple CDN profiles if you want to use a mix of Azure CDN pricing tiers. To create a CDN profile, see [Create a new CDN profile](cdn-create-new-endpoint.md#create-a-new-cdn-profile).
 
-## Log in to the Azure portal
-Log in to the [Azure portal](https://portal.azure.com) with your Azure account.
+## Sign in to the Azure portal
+
+Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
 
 ## Create a new CDN endpoint
 
@@ -94,13 +94,13 @@ Log in to the [Azure portal](https://portal.azure.com) with your Azure account.
     - For **Azure CDN Standard from Akamai** profiles, propagation usually completes within one minute. 
     - For **Azure CDN Standard from Verizon** and **Azure CDN Premium from Verizon** profiles, propagation usually completes within 30 minutes. 
 
-    If you attempt to use the CDN domain name before the endpoint configuration has propagated to the point-of-presence (POP) servers, you might receive an HTTP 404 response status. If it's been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure CDN endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md).
+    If you attempt to use the CDN domain name before the endpoint configuration has propagated to the point-of-presence (POP) servers, you might receive an HTTP 404 response status. If it has been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure CDN endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md).
 
 > [!NOTE]
 > For *Verizon CDN endpoints*, when an endpoint is **disabled** or **stopped** for any reason, all resources configured through the Verizon supplemental portal will be cleaned up. These configurations can't be restored automatically by restarting the endpoint. You will need to make those configuration changes again.
 
 ## Clean up resources
-To delete an endpoint when it is no longer needed, select it and then select **Delete**. 
+To delete an endpoint when it's no longer needed, select it and then select **Delete**. 
 
 ## Next steps
 To learn about custom domains, continue to the tutorial for adding a custom domain to your CDN endpoint.

articles/cdn/cdn-improve-performance.md

@@ -2,27 +2,24 @@
 title: Improve performance by compressing files in Azure CDN | Microsoft Docs
 description: Learn how to improve file transfer speed and increase page-load performance by compressing your files in Azure CDN.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
+manager: kumudd
 ms.assetid: af1cddff-78d8-476b-a9d0-8c2164e4de5d
 ms.service: azure-cdn
 ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 02/28/2018
+ms.date: 02/27/2023
 ms.author: duau
 
 ---
 # Improve performance by compressing files in Azure CDN
-File compression is a simple and effective method to improve file transfer speed and increase page-load performance by reducing a file's size before it is sent from the server. File compression can reduce bandwidth costs and provide a more responsive experience for your users.
+File compression is a simple and effective method to improve file transfer speed and increase page-load performance by reducing a file's size before it's sent from the server. File compression can reduce bandwidth costs and provide a more responsive experience for your users.
 
 There are two ways to enable file compression:
 
 - Enable compression on your origin server. In this case, Azure CDN passes along the compressed files and delivers them to clients that request them.
-- Enable compression directly on the CDN POP servers (*compression on the fly*). In this case, the CDN compresses the files and serves them to the end users, even if they were not compressed by the origin server.
+- Enable compression directly on the CDN POP servers (*compression on the fly*). In this case, the CDN compresses the files and serves them to the end users, even if they don't get compressed by the origin server.
 
 > [!IMPORTANT]
 > Azure CDN configuration changes can take some time to propagate through the network: 
@@ -105,7 +102,7 @@ If the request supports more than one compression type, brotli compression takes
 
 When a request for an asset specifies gzip compression and the request results in a cache miss, Azure CDN performs gzip compression of the asset directly on the POP server. Afterward, the compressed file is served  from the cache.
 
-If the origin uses Chunked Transfer Encoding (CTE) to send compressed data to the CDN POP, then response sizes greater than 8MB are not supported. 
+If the origin uses Chunked Transfer Encoding (CTE) to send compressed data to the CDN POP, then response sizes greater than 8 MB aren't supported. 
 
 ### Azure CDN from Verizon profiles
 
@@ -118,13 +115,13 @@ These profiles support the following compression encodings:
 - DEFLATE
 - bzip2
 
-Azure CDN from Verizon does not support brotli compression. When the HTTP request has the header `Accept-Encoding: br`, the CDN responds with an uncompressed response.
+Azure CDN from Verizon doesn't support brotli compression. When the HTTP request has the header `Accept-Encoding: br`, the CDN responds with an uncompressed response.
 
 ### Azure CDN Standard from Akamai profiles
 
 For **Azure CDN Standard from Akamai** profiles, all files are eligible for compression. However, a file must be of a MIME type that has been [configured for compression](#enabling-compression).
 
-These profiles support gzip compression encoding only. When a profile endpoint requests a gzip-encoded file, it is always requested from the origin, regardless of the client request. 
+These profiles support gzip compression encoding only. When a profile endpoint requests a gzip-encoded file, it's always requested from the origin, regardless of the client request. 
 
 ## Compression behavior tables
 The following tables describe Azure CDN compression behavior for every scenario:

articles/cdn/cdn-msft-http-debug-headers.md

@@ -1,22 +1,19 @@
 ---
 title:  Debug HTTP headers for Azure CDN from Microsoft | Microsoft Docs
-description: Debug cache request headers provides additional information about the cache policy applied to the requested asset. These headers are specific to Azure CDN from Microsoft.
+description: Debug cache request headers provide additional information about the cache policy applied to the requested asset. These headers are specific to Azure CDN from Microsoft.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
-ms.assetid: 
+manager: kumudd
 ms.service: azure-cdn
 ms.workload: media
 ms.tgt_pltfrm: na
 ms.topic: article
-ms.date: 07/31/2019
+ms.date: 02/27/2023
 ms.author: duau
 
 ---
 # Debug HTTP header for Azure CDN from Microsoft
+
 The debug response header, `X-Cache`, provides details as to what layer of the CDN stack the content was served from. This header is specific to Azure CDN from Microsoft.
 
 ### Response header format
@@ -25,9 +22,9 @@ Header | Description
 -------|------------
 X-Cache: TCP_HIT | This header is returned when the content is served from the CDN edge cache. 
 X-Cache: TCP_REMOTE_HIT | This header is returned when the content is served from the CDN regional cache (Origin shield layer)
-X-Cache: TCP_MISS | This header is returned when there is a cache miss, and the content is served from the Origin.
-X-Cache: PRIVATE_NOSTORE | This header is returned when the request cannot be cached as Cache-Control response header is set to either private or no-store.
+X-Cache: TCP_MISS | This header is returned when there's a cache miss, and the content is served from the Origin.
+X-Cache: PRIVATE_NOSTORE | This header is returned when the request can't be cached as Cache-Control response header is set to either private or no-store.
 X-Cache: CONFIG_NOCACHE | This header is returned when the request is configured not to cache in the CDN profile.
-X-Cache: N/A | This header is returned when the request that was denied by Signed URL and Rules Set.
+X-Cache: N/A | This header is returned when a request gets denied by Signed URL and Rules Set.
 
-For additional information on HTTP headers supported in Azure CDN, see [Front Door to backend](../frontdoor/front-door-http-headers-protocol.md#from-the-front-door-to-the-backend).
+For more information on HTTP headers supported in Azure CDN, see [Front Door to backend](../frontdoor/front-door-http-headers-protocol.md#from-the-front-door-to-the-backend).

articles/cdn/cdn-pop-list-api.md

@@ -2,32 +2,29 @@
 title: Retrieve the current POP IP list for Azure CDN| Microsoft Docs
 description: Learn how to get POP servers by using the REST API. POP servers make requests to origin servers associated with Azure Content Delivery Network endpoints.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
-ms.assetid: 
+manager: kumudd
 ms.service: azure-cdn
 ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.topic: article
-ms.date: 07/06/2021
+ms.date: 02/27/2023
 ms.author: duau
 ms.custom: 
 
 ---
+
 # Retrieve the current POP IP list for Azure CDN
 
 ## Retrieve the current Verizon POP IP list for Azure CDN
 
-You can use the REST API to retrieve the set of IPs for Verizon’s point of presence (POP) servers. These POP servers  make requests to origin servers that are associated with Azure Content Delivery Network (CDN) endpoints on a Verizon profile (**Azure CDN Standard from Verizon** or **Azure CDN Premium from Verizon**). Note that this set of IPs is different from the IPs that a client would see when making requests to the POPs. 
+You can use the REST API to retrieve the set of IPs for Verizon’s point of presence (POP) servers. These POP servers  make requests to origin servers that are associated with Azure Content Delivery Network (CDN) endpoints on a Verizon profile (**Azure CDN Standard from Verizon** or **Azure CDN Premium from Verizon**). This set of IPs is different from the IPs that a client would see when making requests to the POPs. 
 
 For the syntax of the REST API operation for retrieving the POP list, see [Edge Nodes - List](/rest/api/cdn/edge-nodes/list).
 
 ## Retrieve the current Microsoft POP IP list for Azure CDN
 
-To lock down your application to accept traffic only from Azure CDN from Microsoft, you will need to set up IP ACLs for your backend. You may also restrict the set of accepted values for the header 'X-Forwarded-Host' sent by Azure CDN from Microsoft. These steps are detailed out as below:
+To lock down your application to accept traffic only from Azure CDN from Microsoft, you need to set up IP ACLs for your backend. You may also restrict the set of accepted values for the header 'X-Forwarded-Host' sent by Azure CDN from Microsoft. These steps are detailed as followed:
 
 Configure IP ACLing for your backends to accept traffic from Azure CDN from Microsoft's backend IP address space and Azure's infrastructure services only. 
 

articles/cdn/cdn-standard-rules-engine.md

@@ -1,11 +1,11 @@
 ---
 title: Use a rules engine to enforce HTTPS in Standard Azure CDN | Microsoft Docs
-description: Use the rules engine for Microsoft Standard Azure Content Delivery Network (Azure CDN) to customize how Azure CDN handles HTTP requests, including blocking the delivery of certain types of content, defining a caching policy, and modifying HTTP headers. In this article, learn how to create a rule to redirect users to HTTPS.
+description: Use the rules engine for Microsoft Standard Azure Content Delivery Network (Azure CDN) to customize how Azure CDN handles HTTP requests. Including blocking the delivery of certain types of content, defining a caching policy, and modifying HTTP headers. In this article, learn how to create a rule to redirect users to HTTPS.
 services: cdn
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 11/01/2019
+ms.date: 02/27/2023
 ms.author: duau
 
 ---