address warning

Author: greg-lindsay

articles/application-gateway/parameter-based-path-selection-portal.md

@@ -30,7 +30,7 @@ For this example, you have a shopping website and the product category is passed
 
 **Step 1:**  Create a path-map as shown in the following image:
 
-    :::image type="content" source="./media/rewrite-http-headers-url/url-scenario1-1.png" alt-text="A screenshot of URL rewrite scenario 1-1.":::
+:::image type="content" source="./media/rewrite-http-headers-url/url-scenario1-1.png" alt-text="A screenshot of URL rewrite scenario 1-1.":::
 
 **Step 2 (a):** Create a rewrite set which has 3 rewrite rules: 
 
@@ -45,7 +45,7 @@ For this example, you have a shopping website and the product category is passed
 
 **Step 2 (b):** Associate this rewrite set with the default path of the previous path-based rule:
 
-    :::image type="content" source="./media/rewrite-http-headers-url/url-scenario1-3.png" alt-text="A screenshot of URL rewrite scenario 1-3.":::
+:::image type="content" source="./media/rewrite-http-headers-url/url-scenario1-3.png" alt-text="A screenshot of URL rewrite scenario 1-3.":::
 
 If the user requests *contoso.com/listing?category=any*, then it's matched with the default path since none of the path patterns in the path map (/listing1, /listing2, /listing3) are matched. Since you associated the previous rewrite set with this path, this rewrite set is evaluated. Because the query string doesn't match the condition in any of the 3 rewrite rules in this rewrite set, no rewrite action takes place. Therefore, the request is routed unchanged to the backend associated with the default path (which is *GenericList*).