Merge pull request #298530 from halkazwini/cdn-freshness

CDN freshness

Author: prmerger-automator[bot]

articles/cdn/scripts/cli/cdn-azure-cli-create-endpoint.md

@@ -4,19 +4,20 @@ description: The Azure CLI sample scripts to create an Azure Content Delivery Ne
 author: halkazwini
 ms.author: halkazwini
 manager: kumudd
-ms.date: 03/20/2024
-ms.topic: sample
 ms.service: azure-cdn
+ms.topic: sample
+ms.date: 04/21/2025
 ms.devlang: azurecli
 ms.custom: devx-track-azurecli
 ms.tool: azure-cli
+ROBOTS: NOINDEX
 ---
 
 # Create an Azure Content Delivery Network profile and endpoint using the Azure CLI
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../../../includes/cdn-classic-retirement.md)]
 
-As an alternative to the Azure portal, you can use these sample the Azure CLI scripts to manage the following content delivery network operations:
+As an alternative to the Azure portal, you can use these sample Azure CLI scripts to manage the following content delivery network operations:
 
 - Create a content delivery network profile.
 - Create a content delivery network endpoint.

articles/frontdoor/standard-premium/how-to-compression.md

@@ -1,11 +1,12 @@
 ---
-title: Improve performance by compressing files in Azure Front Door
+title: Improve performance by compressing files 
+titleSuffix: Azure Front Door
 description: Learn how to improve file transfer speed and increase page-load performance by compressing your files in Azure Front Door.
 author: halkazwini
 ms.author: yuajia
 ms.service: azure-frontdoor
 ms.topic: article
-ms.date: 04/21/2024
+ms.date: 04/21/2025
 ---
 
 # Improve performance by compressing files in Azure Front Door
@@ -21,7 +22,7 @@ There are two ways to enable file compression:
 > Range requests may be compressed into different sizes. Azure Front Door requires the `Content-Length` response header values to be the same for any GET HTTP request. If clients send byte range requests with the `Accept-Encoding` header that leads to the origin responding with different content lengths, then Azure Front Door returns a 503 error. You can either disable compression on the origin/Azure Front Door, or create a Rules Engine rule to remove the `Accept-Encoding` header from byte range requests.
 
 > [!IMPORTANT]
-> Azure Front Door configuration changes takes up to 10 mins to propagate throughout the network. If you're setting up compression for the first time for your CDN endpoint, consider waiting 1-2 hours before you troubleshoot to ensure the compression settings have propagated to all the POPs.
+> Azure Front Door configuration changes take up to 10 mins to propagate throughout the network. If you're setting up compression for the first time for your CDN endpoint, consider waiting 1-2 hours before you troubleshoot to ensure the compression settings have propagated to all the POPs.
 
 ## Enabling compression