more edits

Author: ktoliver

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

@@ -13,7 +13,7 @@ ms.author: magattus
 
 # Actions in the Standard rules engine for Azure CDN
 
-In the [Standard rules engine](cdn-standard-rules-engine.md) for Azure Content Delivery Network (Azure CDN), a rule consists of a set of match conditions and an action. This article provides detailed descriptions of the actions you can use in the Standard rules engine for Azure CDN.
+In the [Standard rules engine](cdn-standard-rules-engine.md) for Azure Content Delivery Network (Azure CDN), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the actions you can use in the Standard rules engine for Azure CDN.
 
 The second part of a rule is an action. An action defines the behavior that's applied to the request type that a match condition or set of match conditions identifies.
 
@@ -29,7 +29,7 @@ Use this action to overwrite the time to live (TTL) value of the endpoint for re
 
 Cache behavior |  Description              
 ---------------|----------------
-Bypass Cache | When this option is selected and the rule matches, the content is not cached.
+Bypass cache | When this option is selected and the rule matches, the content is not cached.
 Override | When this option is selected and the rule matches, the TTL value returned from your origin is overwritten with the value specified in the action.
 Set if missing | When this option is selected and the rule matches, if no TTL value was returned from your origin, the rule sets the TTL to the value specified in the action.
 
@@ -62,7 +62,7 @@ Action | HTTP header name | Value
 -------|------------------|------
 Append | When this option is selected and the rule matches, the header specified in **Header name** is added to the request with the specified value. If the header is already present, the value is appended to the existing value. | String
 Overwrite | When this option is selected and the rule matches, the header specified in **Header name** is added to the request with the specified value. If the header is already present, the specified value overwrites the existing value. | String
-Delete | When this option is selected and the rule matches, and the header specified in the rule is present, the header is deleted from the request. | String
+Delete | When this option is selected, the rule matches, and the header specified in the rule is present, the header is deleted from the request. | String
 
 ### Modify response header
 
@@ -72,9 +72,9 @@ Use this action to modify headers that are present in responses returned to your
 
 Action | HTTP Header name | Value
 -------|------------------|------
-Append | When this option is selected and the rule matches, the header specified in **Header name** is added to the response using the specified **Value**. If the header is already present, **Value** is appended to the existing value. | String
-Overwrite | When this option is selected and the rule matches, the header specified in **Header name** is added to the response using the specified **Value**. If the header is already present, **Value** overwrites the existing value. | String
-Delete | When this option is selected and the rule matches, and the header specified in the rule is present, the header is deleted from the response. | String
+Append | When this option is selected and the rule matches, the header specified in **Header name** is added to the response by using the specified **Value**. If the header is already present, **Value** is appended to the existing value. | String
+Overwrite | When this option is selected and the rule matches, the header specified in **Header name** is added to the response by using the specified **Value**. If the header is already present, **Value** overwrites the existing value. | String
+Delete | When this option is selected, the rule matches, and the header specified in the rule is present, the header is deleted from the response. | String
 
 ### URL redirect
 
@@ -84,11 +84,11 @@ Use this action to redirect clients to a new URL.
 
 Field | Description 
 ------|------------
-Type | Select the response type to return to the requestor. Options are: Found (302), Moved (301), Temporary redirect (307), and Permanent redirect (308).
-Protocol | Match Request, HTTP, or HTTPS.
-Hostname | Select the hostname you want the request to be redirected to. Leave blank to preserve the incoming host.
+Type | Select the response type to return to the requestor: Found (302), Moved (301), Temporary redirect (307), and Permanent redirect (308).
+Protocol | Match Request, HTTP, HTTPS.
+Hostname | Select the host name you want the request to be redirected to. Leave blank to preserve the incoming host.
 Path | Define the path to use in the redirect. Leave blank to preserve the incoming path.  
-Query String | Define the query string used in the redirect. Leave blank to preserve the incoming query string. 
+Query string | Define the query string used in the redirect. Leave blank to preserve the incoming query string. 
 Fragment | Define the fragment to use in the redirect. Leave blank to preserve the incoming fragment. 
 
 We highly recommend that you use an absolute URL. Using a relative URL might redirect Azure CDN URLs to an invalid path. 
@@ -101,9 +101,9 @@ Use this action to rewrite the path of a request that's en route to your origin.
 
 Field | Description 
 ------|------------
-Source Pattern | Define the source pattern in the URL path to replace. Currently, source pattern uses a prefix-based match. To match all URL paths, use “/” as the source pattern value.
+Source pattern | Define the source pattern in the URL path to replace. Currently, source pattern uses a prefix-based match. To match all URL paths, use a forward slash (**/**) as the source pattern value.
 Destination | Define the destination path to use in the rewrite. The destination path overwrites the source pattern.
-Preserve unmatched path | If **Yes**, the remaining path after the source pattern is appended to the new destination path. 
+Preserve unmatched path | If set to **Yes**, the remaining path after the source pattern is appended to the new destination path. 
 
 ## Next steps
 

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

@@ -13,13 +13,13 @@ ms.author: magattus
 
 # Match conditions in the Standard rules engine for Azure CDN
 
-In the [Standard rules engine](cdn-standard-rules-engine.md) for Azure Content Delivery Network (Azure CDN), a rule consists of a set of match conditions and an action. This article provides detailed descriptions of the match conditions you can use in the Standard rules engine for Azure CDN.
+In the [Standard rules engine](cdn-standard-rules-engine.md) for Azure Content Delivery Network (Azure CDN), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the match conditions you can use in the Standard rules engine for Azure CDN.
 
 The first part of a rule is a match condition or set of match conditions. In the Standard rules engine for Azure CDN, each rule can have up to four match conditions. A match condition identifies specific types of requests for which defined actions are performed. If you use multiple match conditions, the match conditions are grouped together by using AND logic.
 
 For example, you can use a match condition to:
 
-- Filter requests that are generated from a specific IP address, country, or region.
+- Filter requests based on a specific IP address, country, or region.
 - Filter requests by header information.
 - Filter requests from mobile devices or desktop devices.
 
@@ -29,7 +29,7 @@ The following match conditions are available to use in the Standard rules engine
 
 ### Device type 
 
-Identifies requests made from a mobile device or desktop device based on the properties of the request.  
+Identifies requests made from a mobile device or desktop device.  
 
 #### Required fields
 
@@ -64,7 +64,7 @@ String | [Standard operator list](#standard-operator-list) | String, Int | No tr
 - Cookie name comparisons are case-insensitive.
 - To specify multiple cookie values, use a single space between each cookie value. 
 - Cookie values can take advantage of wildcard values.
-- If a wildcard value hasn't been specified, only an exact match will satisfy this match condition. For example, "Value" will match "Value" but not "Value1". 
+- If a wildcard value hasn't been specified, only an exact match satisfies this match condition. For example, "Value" will match "Value" but not "Value1". 
 
 ### Post argument
 
@@ -104,7 +104,7 @@ Not IP Match | IP address (space-separated)
 #### Key information
 
 - Use CIDR notation.
-- To specify multiple IP addresses and IP address blocks, use a single space between the values. For example:
+- To specify multiple IP addresses and IP address blocks, use a single space between the values:
   - **IPv4 example**: *1.2.3.4 10.20.30.40* matches any requests that arrive from either address 1.2.3.4 or 10.20.30.40.
   - **IPv6 example**: *1:2:3:4:5:6:7:8 10:20:30:40:50:60:70:8*0 matches any requests that arrive from either address 1:2:3:4:5:6:7:8 or 10:20:30:40:50:60:70:80.
 - The syntax for an IP address block is the base IP address followed by a forward slash and the prefix size. For example:
@@ -133,11 +133,11 @@ String | [Standard operator list](#standard-operator-list) | String, Int | No tr
 
 ### Request method
 
-Identifies requests based on the request method used in the request.
+Identifies requests that use the specified request method.
 
 #### Required fields
 
-Operator | Supported value
+Operator | Supported values
 ---------|----------------
 Equals, Not equals | GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE
 
@@ -147,17 +147,17 @@ Equals, Not equals | GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE
 
 ### Request protocol
 
-Identifies requests based on the protocol used to send the request.
+Identifies requests that use the specified protocol used.
 
 #### Required fields
 
-Operator | Supported value
+Operator | Supported values
 ---------|----------------
 Equals, Not equals | HTTP, HTTPS
 
 ### Request URL
 
-Identifies requests based on the URL used to send the request.
+Identifies requests that match the specified URL.
 
 #### Required fields
 
@@ -171,7 +171,7 @@ Operator | Request URL | Case transform
 
 ### URL file extension
 
-Identifies requests based on the file extension of the file name part of the requesting URL.
+Identifies requests that include the specified file extension in the file name in the requesting URL.
 
 #### Required fields
 
@@ -185,7 +185,7 @@ Operator | Extension | Case transform
 
 ### URL file name
 
-Identifies requests based on the file name part of the requesting URL.
+Identifies requests that include the specified file name in the requesting URL.
 
 #### Required fields
 
@@ -199,7 +199,7 @@ Operator | File name | Case transform
 
 ### URL path
 
-Identifies requests based on the path of the requesting URL.
+Identifies requests that include the specified path in the requesting URL.
 
 #### Required fields
 
@@ -215,7 +215,7 @@ Operator | Value | Case Transform
 
 ### Standard operator list
 
-For rules that contain the standard operator list, the following operators are valid:
+For rules that accept values from the standard operator list, the following operators are valid:
 
 - Any
 - Equals