fixed blocking issues

Author: duongau

articles/cdn/akamai-retirement-faq.md

@@ -49,7 +49,7 @@ For Azure Traffic Manager users with Multi-CDN:
 
 > [!TIP]
 > Items to validate related migration:
-> - HTTPS with Managed Certificate. To provision a managed certificate, you must CNAME your custom domain to an `azureedge.net`` endpoint. If you have changed the CNAME of your custom domain, check your HTTPS status and wait for the provisioning to complete.
+> - HTTPS with Managed Certificate. To provision a managed certificate, you must CNAME your custom domain to an `azureedge.net` endpoint. If you have changed the CNAME of your custom domain, check your HTTPS status and wait for the provisioning to complete.
 > - Azure CDN Standard from Edgio offers enhanced reporting and origin configuration options. You can access them by selecting the **Managed** button.
 
 ## Next steps

articles/cdn/cdn-add-to-web-app.md

@@ -94,7 +94,8 @@ Navigate a browser to the following URL:
 
 `http://<endpointname>.azureedge.net/index.html`
 
-![Sample app home page served from content delivery network](media/cdn-add-to-web-app/sample-app-home-page-cdn.png)
+:::image type="content" source="media/cdn-add-to-web-app/sample-app-home-page-cdn.png" alt-text="Screenshot of sample app home page served from content delivery network.":::
+
 
 You see the same page that you ran earlier in an Azure web app. Azure Content Delivery Network has retrieved the origin web app's assets and is serving them from the content delivery network endpoint
 
@@ -135,7 +136,7 @@ If you browse to the content delivery network endpoint URL for the home page, yo
 
 `http://<endpointname>.azureedge.net/index.html`
 
-![No V2 in title in content delivery network](media/cdn-add-to-web-app/no-v2-in-cdn-title.png)
+:::image type="content" source="media/cdn-add-to-web-app/no-v2-in-cdn-title.png" alt-text="Screenshot of No V2 in title in content delivery network.":::
 
 <a name='purge-the-cdn-in-the-portal'></a>
 
@@ -173,7 +174,7 @@ When you browse to the content delivery network endpoint URL for *index.html*, y
 
 `http://<endpointname>.azureedge.net/index.html`
 
-![V2 in title in content delivery network](media/cdn-add-to-web-app/v2-in-cdn-title.png)
+:::image type="content" source="media/cdn-add-to-web-app/v2-in-cdn-title.png" alt-text="Screenshot of V2 in title V2 in title in content delivery network.":::
 
 For more information, see [Purge an Azure Content Delivery Network endpoint](../cdn/cdn-purge-endpoint.md).
 
@@ -220,11 +221,11 @@ In a browser, go to the content delivery network endpoint URL with a new query s
 
 `http://<endpointname>.azureedge.net/index.html?q=2`
 
-![V3 in title in content delivery network, query string 2](media/cdn-add-to-web-app/v3-in-cdn-title-qs2.png)
+:::image type="content" source="media/cdn-add-to-web-app/v3-in-cdn-title-qs2.png" alt-text="Screenshot of V3 in title in content delivery network, query string 2.":::
 
 `http://<endpointname>.azureedge.net/index.html?q=1`
 
-![V2 in title in content delivery network, query string 1](media/cdn-add-to-web-app/v2-in-cdn-title-qs1.png)
+:::image type="content" source="media/cdn-add-to-web-app/v2-in-cdn-title-qs1.png" alt-text="Screenshot of V2 in title in content delivery network, query string 1.":::
 
 This output shows that each query string is treated differently:
 

articles/cdn/cdn-advanced-http-reports.md

@@ -182,7 +182,7 @@ The left-hand side of the graph (y-axis) indicates the file name for each of the
 Directly below the bar chart, the following information is listed for the top 250 requested assets: relative path (including file name), the number of times that it gets downloaded to completion, the number of times that it gets requested, and the percentage of requests that resulted in a complete download.
 
 > [!TIP]
-> Our CDN is not informed by an HTTP client (that is, browser) when an asset has been completely downloaded. As a result, we have to calculate whether an asset has been completely downloaded according to status codes and byte-range requests. The first thing we look for when making this calculation is whether a request results in a 200 OK status code. If so, then we look at byte-range requests to ensure that they cover the entire asset. Finally, we compare the amount of data transferred to the size of the requested asset. If the data transferred is equal to or greater than the file size and the byte-range requests are appropriate for that asset, then the hit will be counted as a complete download.
+> Our content delivery network is not informed by an HTTP client (that is, browser) when an asset has been completely downloaded. As a result, we have to calculate whether an asset has been completely downloaded according to status codes and byte-range requests. The first thing we look for when making this calculation is whether a request results in a 200 OK status code. If so, then we look at byte-range requests to ensure that they cover the entire asset. Finally, we compare the amount of data transferred to the size of the requested asset. If the data transferred is equal to or greater than the file size and the byte-range requests are appropriate for that asset, then the hit will be counted as a complete download.
 >
 > Due to the interpretive nature of this report, you should keep in mind the following points that may alter the consistency and accuracy of this report.
 >
@@ -199,7 +199,7 @@ The By 404 Errors report allows you to identify the type of content that generat
 > For the purposes of this report, note the following:
 >
 > - A hit represents any request for an asset regardless of status code.
-> - Edge CNAME URLs are converted to their equivalent CDN URLs. This allows an accurate tally for all statistics associated with an asset regardless of the CDN or edge CNAME URL used to request it.
+> - Edge CNAME URLs are converted to their equivalent content delivery network URLs. This allows an accurate tally for all statistics associated with an asset regardless of the content delivery network or edge CNAME URL used to request it.
 >
 >
 
@@ -209,7 +209,7 @@ Directly below the bar chart, the following information is listed for the top 25
 
 ## See also
 
-- [Azure CDN Overview](cdn-overview.md)
-- [Real-time stats in Microsoft Azure CDN](cdn-real-time-stats.md)
+- [Azure Content Delivery Network Overview](cdn-overview.md)
+- [Real-time stats in Microsoft Azure Content Delivery Network](cdn-real-time-stats.md)
 - [Overriding default HTTP behavior using the rules engine](./cdn-verizon-premium-rules-engine.md)
 - [Analyze Edge Performance](cdn-edge-performance.md)

articles/cdn/cdn-analyze-usage-patterns.md

@@ -131,7 +131,7 @@ The formula is: (TCP_ HIT/(TCP_ HIT+TCP_MISS))*100
 
 This report shows the traffic usage distribution in IPv4 vs IPv6.
 
-![IPv4/IPv6 Data transferred](./media/cdn-reports/cdn-ipv4-ipv6.png)
+:::image type="content" source="./media/cdn-reports/cdn-ipv4-ipv6.png" alt-text="Screenshot of IPv4/IPv6 Data transferred.":::
 
 ## Considerations
 

articles/cdn/cdn-app-dev-node.md

@@ -38,7 +38,8 @@ npm init
 
 You will then be presented a series of questions to initialize your project. For **entry point**, this tutorial uses *app.js*. You can see my other choices in the following example.
 
-![Npm init output](./media/cdn-app-dev-node/cdn-npm-init.png)
+:::image type="content" source="./media/cdn-app-dev-node/cdn-npm-init.png" alt-text="Screenshot of NPM init output.":::
+
 
 Our project is now initialized with a *packages.json* file. Our project is going to use some Azure libraries contained in npm packages. We'll use the library for Microsoft Entra authentication in Node.js (@Azure/identity) and the Azure CDN Client Library for JavaScript (@Azure/Azure Resource Manager-cdn). Let's add those to the project as dependencies.
 

articles/cdn/cdn-azure-diagnostic-logs.md

@@ -40,7 +40,7 @@ Follow these steps enable logging for your Azure Content Delivery Network endpoi
 
 2. Select the content delivery network endpoint for which you want to enable diagnostics logs:
 
-    :::image type="content" source="./media/cdn-diagnostics-log/02_browse-to-diagnostics-logs.png" alt-text="Select content delivery network endpoint." border="true":::
+    :::image type="content" source="./media/cdn-diagnostics-log/02_browse-to-diagnostics-logs.png" alt-text="Screenshot of select content delivery network endpoint." border="true":::
 
 3. Select **Diagnostics logs** in the **Monitoring** section:
 

articles/cdn/cdn-billing.md

@@ -59,15 +59,15 @@ If you're using Azure Blob storage as the origin for your content, you also incu
 - Transfers in GB: The amount of data transferred to fill the content delivery network caches.
 
 > [!NOTE]
-> Starting October 2019, If you are using Azure Content Delivery Network from Microsoft, the cost of data transfer from Origins hosted in Azure to content delivery network PoPs is free of charge. Azure Content Delivery Network from Edgio is subject to the rates described as followed.
+> Starting October 2019, if you are using Azure Content Delivery Network from Microsoft, the cost of data transfer from origins hosted in Azure to content delivery network PoPs is free of charge. Azure Content Delivery Network from Edgio is subject to the rates described as followed.
 
 For more information about Azure Storage billing, see [Plan and manage costs for Azure Storage](../storage/common/storage-plan-manage-costs.md).
 
 If you're using *hosted service delivery*, you incur charges as follows:
 
 - Azure compute time: The compute instances that act as the origin.
 
-- Azure compute transfer: The data transfers from the compute instances to fill the Azure content delivery network caches.
+- Azure compute transfer: The data transfers from the compute instances to fill the Azure Content Delivery Network caches.
 
 If your client uses byte-range requests (regardless of origin service), the following considerations apply:
 

articles/cdn/cdn-caching-policy.md

@@ -13,18 +13,18 @@ ms.author: juliako
 
 # Manage Azure CDN caching policy in Azure Media Services
 
-Azure Media Services provides HTTP based Adaptive Streaming and progressive download. HTTP based streaming is highly scalable with benefits of caching in proxy and CDN layers as well as client-side caching. Streaming endpoints provides general streaming capabilities and also configuration for HTTP cache headers. Streaming endpoints sets HTTP Cache-Control: max-age and Expires headers. You can get more information for HTTP cache headers from [W3.org](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html).
+Azure Media Services provides HTTP based Adaptive Streaming and progressive download. HTTP based streaming is highly scalable with benefits of caching in proxy and CDN layers and client-side caching. Streaming endpoints provides general streaming capabilities and also configuration for HTTP cache headers. Streaming endpoints sets HTTP Cache-Control: max-age and Expires headers. You can get more information for HTTP cache headers from [W3.org](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html).
 
 ## Default Caching headers
 
-By default streaming-endpoints apply 3 day cache headers for on-demand streaming data (actual media fragments/chunks) and manifest(playlist). For live streaming, streaming endpoints apply 3 day cache headers for data (actual media fragments/chunks) and 2 seconds cache header for manifest(playlist) requests. When live program turns to on-demand (live archive), then on-demand streaming cache headers apply.
+By default streaming-endpoints apply three day cache headers for on-demand streaming data (actual media fragments/chunks) and manifest(playlist). For live streaming, streaming endpoints apply three day cache headers for data (actual media fragments/chunks) and 2-seconds cache header for manifest(playlist) requests. When live program turns to on-demand (live archive), then on-demand streaming cache headers apply.
 
 ## Azure CDN integration
 
-Azure Media Services provides [integrated CDN](https://azure.microsoft.com/updates/azure-media-services-now-fully-integrated-with-azure-cdn/) for streaming-endpoints. Cache-control headers applies in the same way as streaming endpoints to CDN enabled streaming endpoints. Azure CDN uses streaming endpoint configured cache values to define the life time of the internally cached objects and also uses this value to set the delivery cache headers. When using CDN enabled streaming endpoints it is not recommended to set small cache values. Setting small values decrease the performance and reduce the benefit of CDN. It is not allowed to set cache headers smaller than 600 seconds for CDN enabled streaming endpoints.
+Azure Media Services provides [integrated CDN](https://azure.microsoft.com/updates/azure-media-services-now-fully-integrated-with-azure-cdn/) for streaming-endpoints. Cache-control headers apply in the same way as streaming endpoints to CDN enabled streaming endpoints. Azure CDN uses streaming endpoint configured cache values to define the life time of the internally cached objects and also uses this value to set the delivery cache headers. When using CDN enabled streaming endpoints, it isn't recommended to set small cache values. Setting small values decrease the performance and reduce the benefit of CDN. It isn't allowed to set cache headers smaller than 600 seconds for CDN enabled streaming endpoints.
 
 > [!IMPORTANT]
-> Azure Media Services has complete integration with Azure CDN. With a single click, you can integrate all the available Azure CDN providers to your streaming endpoint including standard and premium products. For more information, see this [announcement](https://azure.microsoft.com/blog/standardstreamingendpoint/).
+> Azure Media Services has complete integration with Azure Content Delivery Network. With a single click, you can integrate all the available Azure Content Delivery Network providers to your streaming endpoint including standard and premium products. For more information, see this [announcement](https://azure.microsoft.com/blog/standardstreamingendpoint/).
 >
 > Data charges from streaming endpoint to CDN only gets disabled if the CDN is enabled over streaming endpoint APIs or using Azure portal's streaming endpoint section. Manual integration or directly creating a CDN endpoint using CDN APIs or portal section doesn't disable the data charges.
 
@@ -39,5 +39,5 @@ You can use Azure portal or Azure Media Services APIs to configure cache header
 ## Cache configuration precedence order
 
 1. Azure Media Services configured cache value overrides default value.
-2. If there is no manual configuration, default values apply.
-3. By default 2 seconds cache headers applies to live streaming manifest(playlist) regardless of Azure Media or Azure Storage configuration and overriding of this value is not available.
+2. If there's no manual configuration, default values apply.
+3. By default 2-seconds cache headers apply to live streaming manifest(playlist) regardless of Azure Media or Azure Storage configuration and overriding of this value isn't available.

articles/cdn/cdn-caching-rules-tutorial.md

@@ -42,11 +42,12 @@ Before you can complete the steps in this tutorial, you must first create a cont
 
 2. In the left pane under Settings, select **Caching rules**.
 
-   ![Content delivery network Caching rules button](./media/cdn-caching-rules/cdn-caching-rules-btn.png)
+    :::image type="content" source="./media/cdn-caching-rules/cdn-caching-rules-btn.png" alt-text="Screenshot of content delivery network caching rules button.":::
+    
 
    The **Caching rules** page appears.
 
-   ![Content delivery network Caching rules page](./media/cdn-caching-rules/cdn-caching-rules-page.png)
+    :::image type="content" source="./media/cdn-caching-rules/cdn-caching-rules-page.png" alt-text="Screenshot of content delivery network Caching rules page.":::
 
 ## Set global caching rules
 

articles/cdn/cdn-caching-rules.md

@@ -37,11 +37,11 @@ For information about default caching behavior and caching directive headers, se
 
 2. In the left pane under Settings, select **Caching rules**.
 
-   ![Content delivery network Caching rules button](./media/cdn-caching-rules/cdn-caching-rules-btn.png)
+    :::image type="content" source="./media/cdn-caching-rules/cdn-caching-rules-btn.png" alt-text="Screenshot of content delivery networking caching rules.":::
 
    The **Caching rules** page appears.
 
-   ![Content delivery network Caching rules page](./media/cdn-caching-rules/cdn-caching-rules-page.png)
+    :::image type="content" source="./media/cdn-caching-rules/cdn-caching-rules-page.png" alt-text="Screenshot of content delivery network caching rules page.":::
 
 ## Caching behavior settings