updating with fixes again

Author: Maxwell Gattuso

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

@@ -19,6 +19,8 @@ The second part of a rule is an action. An action defines the behavior that is a
 
 ## Actions
 
+The following actions are available to use. 
+
 ## Cache Expiration
 
 This action allows you to overwrite the TTL of the endpoint for requests specified by the rules match conditions.

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

@@ -25,6 +25,8 @@ For example, you can use a match condition to:
 
 ## Match Conditions
 
+The following match conditions are available to use. 
+
 ### Device type 
 
 The Device type match condition identifies requests made from a mobile or desktop device based on its properties.  

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

@@ -27,7 +27,7 @@ The Azure CDN Standard Rules Engine allows you to customize how HTTP requests ar
 
     The Rules Engine blade is displayed, with the Global rule. 
 
-    [![CDN new rules page](./media/cdn-standard-rules-engine/cdn-blank-rule.png)](./media/cdn-standard-rules-engine/cdn-blank-rule.png#lightbox)
+    [![CDN new rules page](./media/cdn-standard-rules-engine/cdn-new-rule.png)](./media/cdn-standard-rules-engine/cdn-new-rule.png#lightbox)
 
    > [!IMPORTANT]
    > The order in which multiple rules are listed affects how they are handled. A subsequent rule may override the actions specified by a previous rule.
@@ -37,15 +37,15 @@ The Azure CDN Standard Rules Engine allows you to customize how HTTP requests ar
 
 4. Identify the type of requests the rule applies to. Use the drop down to select the **Request protocol** match condition, and use the value **Equals** **HTTP**.
 
-   [![CDN rule match condition](./media/cdn-standard-rules-engine/cdn-request-protocol.png)](./media/cdn-standard-rules-engine/cdn-request-protocol.png#lightbox)
+   [![CDN rule match condition](./media/cdn-standard-rules-engine/cdn-match-condition.png)](./media/cdn-standard-rules-engine/cdn-match-condition.png#lightbox)
 
    > [!NOTE]
    > Multiple match conditions are available in the dropdown list. 
    > For a detailed list of match conditions, see [Rules engine match conditions](cdn-standard-rules-engine-match-conditions.md).
    
 5. Choose the action that will be applied to the identified requests. Use the dropdown to select the **URL redirect** action, and use the Value **Found (302)** for Type, and **HTTPS** for protocol. Leave all other fields blank to use the incoming values.
 
-   [![CDN rule action](./media/cdn-standard-rules-engine/cdn-new-action.png)](./media/cdn-standard-rules-engine/cdn-new-action.png#lightbox)
+   [![CDN rule action](./media/cdn-standard-rules-engine/cdn-action.png)](./media/cdn-standard-rules-engine/cdn-action.png#lightbox)
 
    > [!NOTE]
    > Multiple Actions are available in the dropdown list.