task 656: Topic overhaul and new screenshots, add multiple query string note

Author: dksimpson

articles/cdn/cdn-query-string-premium.md

@@ -13,7 +13,7 @@ ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 01/23/2017
+ms.date: 11/09/2017
 ms.author: mazha
 
 ---
@@ -25,34 +25,32 @@ ms.author: mazha
 > 
 
 ## Overview
-Query string caching controls how files are to be cached when they contain query strings.
+Query string caching controls how files are cached when a request contains query strings. For example, \http://www.domain.com/content.mov?data=true. If there is more than one query string in a request, the order of the query strings does not matter.
 
 > [!IMPORTANT]
-> The Standard and Premium CDN products provide the same query string caching functionality, but the user interface differs.  This document describes the interface for **Azure CDN Premium from Verizon**.  For query string caching with **Azure CDN Standard from Akamai** and **Azure CDN Standard from Verizon**, see [Controlling caching behavior of CDN requests with query strings](cdn-query-string.md).
-> 
-> 
+> The standard and premium CDN products provide the same query string caching functionality, but the user interface differs.  This article describes the interface for **Azure CDN Premium from Verizon**.  For query string caching with **Azure CDN Standard from Akamai** and **Azure CDN Standard from Verizon**, see [Controlling caching behavior of CDN requests with query strings](cdn-query-string.md).
+>
 
-Three modes are available:
+Three query string modes are available:
 
-* **standard-cache**:  This is the default mode.  The CDN edge node will pass the query string from the requestor to the origin on the first request and cache the asset.  All subsequent requests for that asset that are served from the edge node will ignore the query string until the cached asset expires.
-* **no-cache**:  In this mode, requests with query strings are not cached at the CDN edge node.  The edge node retrieves the asset directly from the origin and passes it to the requestor with each request.
-* **unique-cache**:  This mode treats each request with a query string as a unique asset with its own cache.  For example, the response from the origin for a request for *foo.ashx?q=bar* would be cached at the edge node and returned for subsequent caches with that same query string.  A request for *foo.ashx?q=somethingelse* would be cached as a separate asset with its own time to live.
+- **standard-cache**: Default mode. In this mode, the CDN edge node passes the query strings from the requestor to the origin on the first request and caches the asset. All subsequent requests for the asset that are served from the edge node ignore the query strings until the cached asset expires.
+- **no-cache**: In this mode, requests with query strings are not cached at the CDN edge node. The edge node retrieves the asset directly from the origin and passes it to the requestor with each request.
+- **unique-cache**: This mode treats each request with query strings as a unique asset with its own cache. For example, the response from the origin for a request for *foo.ashx?q=bar* is cached at the edge node and returned for subsequent caches with the same query strings. A request for *foo.ashx?q=somethingelse* is cached as a separate asset with its own time-to-live setting.
 
 ## Changing query string caching settings for premium CDN profiles
-1. From the CDN profile blade, click the **Manage** button.
+1. From the CDN profile blade, click **Manage**.
 
-    ![CDN profile blade manage button](./media/cdn-query-string-premium/cdn-manage-btn.png)
+    ![CDN profile Manage button](./media/cdn-query-string-premium/cdn-manage-btn.png)
 
     The CDN management portal opens.
-2. Hover over the **HTTP Large** tab, then hover over the **Cache Settings** flyout.  Click on **Query-String Caching**.
+2. Hover over the **HTTP Large** tab, then hover over the **Cache Settings** flyout. Click **Query-String Caching**.
 
     Query string caching options are displayed.
 
     ![CDN query string caching options](./media/cdn-query-string-premium/cdn-query-string.png)
-3. After making your selection, click the **Update** button.
+3. Select a query string mode, then click **Update**.
 
 > [!IMPORTANT]
-> The settings changes may not be immediately visible, as it takes time for the registration to propagate through the CDN.  For <b>Azure CDN from Verizon</b> profiles, propagation will usually complete within 90 minutes, but in some cases can take longer.
-> 
-> 
+> Because it takes time for the registration to propagate through the CDN, cache string settings changes might not be immediately visible. For **Azure CDN Premium from Verizon** profiles, propagation usually completes within 90 minutes, but in some cases can take longer.
+ 
 

articles/cdn/cdn-query-string.md

@@ -1,6 +1,6 @@
 ---
 title: Control Azure CDN caching behavior with query strings | Microsoft Docs
-description: Azure CDN query string caching controls how files are to be cached when they contain query strings.
+description: Azure CDN query string caching controls how files are cached when they contain query strings.
 services: cdn
 documentationcenter: ''
 author: zhangmanling
@@ -13,49 +13,44 @@ ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 01/23/2017
+ms.date: 11/09/2017
 ms.author: mazha
 
 ---
-# Control Azure CDN caching behavior with query strings
+# Control Azure Content Delivery Network caching behavior with query strings
 > [!div class="op_single_selector"]
 > * [Standard](cdn-query-string.md)
 > * [Azure CDN Premium from Verizon](cdn-query-string-premium.md)
 > 
-> 
 
 ## Overview
-Query string caching controls how files are to be cached when they contain query strings.
+Query string caching controls how files are cached when a request contains query strings. For example, \http://www.domain.com/content.mov?data=true. If there is more than one query string in a request, the order of the query strings does not matter.
 
 > [!IMPORTANT]
-> The Standard and Premium CDN products provide the same query string caching functionality, but the user interface differs.  This document describes the interface for **Azure CDN Standard from Akamai** and **Azure CDN Standard from Verizon**.  For query string caching with **Azure CDN Premium from Verizon**, see [Controlling caching behavior of CDN requests with query strings - Premium](cdn-query-string-premium.md).
-> 
-> 
+> The standard and premium CDN products provide the same query string caching functionality, but the user interface differs.  This article describes the interface for **Azure CDN Standard from Akamai** and **Azure CDN Standard from Verizon**. For query string caching with **Azure CDN Premium from Verizon**, see [Controlling caching behavior of CDN requests with query strings - Premium](cdn-query-string-premium.md).
 
-Three modes are available:
+Three query string modes are available:
 
-* **Ignore query strings**:  This is the default mode.  The CDN edge node will pass the query string from the requestor to the origin on the first request and cache the asset.  All subsequent requests for that asset that are served from the edge node will ignore the query string until the cached asset expires.
-* **Bypass caching for URL with query strings**:  In this mode, requests with query strings are not cached at the CDN edge node.  The edge node retrieves the asset directly from the origin and passes it to the requestor with each request.
-* **Cache every unique URL**:  This mode treats each request with a query string as a unique asset with its own cache.  For example, the response from the origin for a request for *foo.ashx?q=bar* would be cached at the edge node and returned for subsequent caches with that same query string.  A request for *foo.ashx?q=somethingelse* would be cached as a separate asset with its own time to live.
+- **Ignore query strings**: Default mode. In this mode, the CDN edge node passes the query strings from the requestor to the origin on the first request and caches the asset. All subsequent requests for the asset that are served from the edge node ignore the query strings until the cached asset expires.
+- **Bypass caching for query strings**: In this mode, requests with query strings are not cached at the CDN edge node. The edge node retrieves the asset directly from the origin and passes it to the requestor with each request.
+- **Cache every unique URL**: In this mode, each request with a query string is treated as a unique asset with its own cache.  For example, the response from the origin for a request for *foo.ashx?q=bar* is cached at the edge node and returned for subsequent caches with the same query string. A request for *foo.ashx?q=somethingelse* is cached as a separate asset with its own time-to-live setting.
 
 ## Changing query string caching settings for standard CDN profiles
-1. From the CDN profile blade, click the CDN endpoint you wish to manage.
+1. Select a CDN profile, then select the CDN endpoint you want to manage.
 
-    ![CDN profile blade endpoints](./media/cdn-query-string/cdn-endpoints.png)
+    ![CDN profile endpoints](./media/cdn-query-string/cdn-endpoints.png)
 
-    The CDN endpoint blade opens.
-2. Click the **Configure** button.
+   The CDN endpoint blade opens.
+2. Under Settings, click **Cache**.
 
-    ![CDN profile blade manage button](./media/cdn-query-string/cdn-config-btn.png)
+    ![CDN profile Cache button](./media/cdn-query-string/cdn-cache-btn.png)
 
-    The CDN Configuration blade opens.
-3. Select a setting from the **Query string caching behavior** dropdown.
+   The CDN cache blade opens.
+3. In the **Query string caching behavior** list, select a query string mode, then click **Save**.
 
-    ![CDN query string caching options](./media/cdn-query-string/cdn-query-string.png)
-4. After making your selection, click the **Save** button.
+  <!--- Replace screen shot after general caching goes live ![CDN query string caching options](./media/cdn-query-string/cdn-query-string.png) --->
 
 > [!IMPORTANT]
-> The settings changes may not be immediately visible, as it takes time for the registration to propagate through the CDN.  For <b>Azure CDN from Akamai</b> profiles, propagation will usually complete within one minute.  For <b>Azure CDN from Verizon</b> profiles, propagation will usually complete within 90 minutes, but in some cases can take longer.
-> 
-> 
+> Because it takes time for the registration to propagate through the CDN, cache string settings changes might not be immediately visible. For **Azure CDN from Akamai** profiles, propagation usually completes within one minute. For **Azure CDN from Verizon** profiles, propagation usually completes within 90 minutes, but in some cases can take longer.
+