tweaks to scenario 2&3

Author: halkazwini

articles/frontdoor/media/rules-engine-scenarios/modify-response-header.png

@@ -196,7 +196,12 @@ Managing redirects is critical for search engine optimization (SEO), user experi
 
 ### Scenario 2: Populate or modify a response header based on a request header value
 
-For example, add CORS header where needed to serve scripts on multiple origins from the same CDN domain, and response must contain the same FQDN in Access-Control-Allow-Origin header as the request Origin header, rather than allowing all domains (*) to enhance security. This can be achieved using {http_req_header_Origin}. 
+In some scenarios, you may need to populate or modify a response header based on a request header value.
+
+For example, you can add CORS header where needed to serve scripts on multiple origins from the same CDN domain, and response must contain the same FQDN in `Access-Control-Allow-Origin` header as the request origin header, rather than a wildcard allowing all domains (*) to enhance security. You can achieve it by using the `{http_req_header_Origin}` server variable to set the response header.
+
+:::image type="content" source="./media/rules-engine-scenarios/modify-response-header.png" alt-text="Screenshot that shows how to modify a response header based on a request header value." lightbox="./media/rules-engine-scenarios/modify-response-header.png":::
+
 
 ```json
 {
@@ -240,9 +245,13 @@ For example, add CORS header where needed to serve scripts on multiple origins f
 }
 ```
 
-### Scenario 3: Rename a response header generated by a cloud provider to a brand-specific one 
+### Scenario 3: Rename a response header to a brand-specific one 
+
+You can rename a response header generated by a cloud provider by adding a new custom response header and deleting the original.
+
+For example, you can replace the response header `X-Azure-Backend-ID` with a brand-specific header `X-Contoso-Scale-ID`.
 
-This can be achieved by adding a new response header and deleting the original. E.g. Scenario: replace the response header X-Azure-Backend-ID with brand specific header ‘X-Contoso-Scale-ID' instead.
+:::image type="content" source="./media/rules-engine-scenarios/rename-response-header-brand-specific.png" alt-text="Screenshot that shows how to rename a response header to a brand-specific one." lightbox="./media/rules-engine-scenarios/rename-response-header-brand-specific.png":::
 
 ```json
 {