Apply suggestions from PCX review

Author: pedrosousa

src/content/changelog/rules/2025-06-09-custom-errors-fetch-4xx-5xx-assets.mdx

@@ -9,8 +9,8 @@ date: 2025-06-09T18:00:00Z
 [Custom Errors](/rules/custom-errors/) can now fetch and store [assets](/rules/custom-errors/create-rules/#create-a-custom-error-asset-dashboard) and [error pages](/rules/custom-errors/#error-pages) from your origin even if they are served with a 4xx or 5xx HTTP status code — previously, only 200 OK responses were allowed.
 
 **What’s new:**
-- You can now upload error pages and error assets that return error status codes (e.g. 403, 500, 502, 503, 504) when fetched
-- These assets are stored and minified at the edge, so they can be reused across multiple Custom Error rules without triggering requests to the origin
+- You can now upload error pages and error assets that return error status codes (for example, 403, 500, 502, 503, 504) when fetched.
+- These assets are stored and minified at the edge, so they can be reused across multiple Custom Error rules without triggering requests to the origin.
 
 This is especially useful for retrieving error content or downtime banners from your backend when you can’t override the origin status code.
 

src/content/changelog/rules/2025-06-09-transform-rule-subrequest-matching.mdx

@@ -8,7 +8,7 @@ date: 2025-06-09T17:00:00Z
 
 import { Example } from "~/components";
 
-You can now use the [cf.worker.upstream_zone](/ruleset-engine/rules-language/fields/reference/cf.worker.upstream_zone/) field in [Transform Rules](/rules/transform/) to control rule execution based on whether a request originates from [Workers](/workers/), including subrequests issued by Workers in other zones.
+You can now use the [`cf.worker.upstream_zone`](/ruleset-engine/rules-language/fields/reference/cf.worker.upstream_zone/) field in [Transform Rules](/rules/transform/) to control rule execution based on whether a request originates from [Workers](/workers/), including subrequests issued by Workers in other zones.
 
 ![Match Workers subrequests by upstream zone in Transform Rules](~/assets/images/changelog/rules/transform-rule-subrequest-matching.png)
 
@@ -20,10 +20,10 @@ For example, to add a header when the subrequest comes from another zone:
 
 <Example>
 
-Text in **Expression Editor** *(replace `myzone.com` with your domain)*:
+Text in **Expression Editor** (replace `myappexample.com` with your domain):
 
 ```txt
-(cf.worker.upstream_zone != "" and cf.worker.upstream_zone != "myzone.com")
+(cf.worker.upstream_zone != "" and cf.worker.upstream_zone != "myappexample.com")
 ```
 
 Selected operation under **Modify request header**: _Set static_

src/content/docs/rules/custom-errors/troubleshooting.mdx

@@ -8,7 +8,7 @@ sidebar:
 
 ## Cannot preview error page
 
-If Cloudflare cannot load your site or you have blocked the United States (US) via [IP Access rules](/waf/tools/ip-access-rules/) or WAF custom rules, publishing and previewing custom error page might not work.
+If Cloudflare cannot load your site or you have blocked the United States (US) via [IP Access rules](/waf/tools/ip-access-rules/) or WAF custom rules, publishing and previewing a custom error page might not work.
 
 A common error might look like the following: `Error fetching page: Fetch failed, https://example.com/ipcountryblock.html returned 403 (Code: 1202)`.
 
@@ -18,9 +18,9 @@ Make sure that no WAF rule is blocking or challenging Custom Errors product when
 
 If you block countries or IP addresses with an [IP Access rule](/waf/tools/ip-access-rules/), affected visitors will get a `1005` error and your **IP/Country Block** custom page.
 
-If you block countries or IP addresses with a [WAF custom rule](/waf/custom-rules/) and you do not configure a [Custom Error rule](/rules/custom-errors/create-rules/#create-a-custom-error-rule-dashboard) or a [WAF custom response](/waf/custom-rules/create-dashboard/#configure-a-custom-response-for-blocked-requests) for blocked requests, affected visitors will get your **WAF Block** page.
+If you block countries or IP addresses with a [WAF custom rule](/waf/custom-rules/) and you do not configure a [custom error rule](/rules/custom-errors/create-rules/#create-a-custom-error-rule-dashboard) or a [WAF custom response](/waf/custom-rules/create-dashboard/#configure-a-custom-response-for-blocked-requests) for blocked requests, affected visitors will get your **WAF Block** page.
 
-If you block requests due to a [rate limiting rule](/waf/rate-limiting-rules/) and you do not configure a [Custom Error rule](/rules/custom-errors/create-rules/#create-a-custom-error-rule-dashboard) or a [WAF custom response](/waf/rate-limiting-rules/create-zone-dashboard/#configure-a-custom-response-for-blocked-requests) for blocked requests, affected visitors will get your **429 Errors** page displaying a Cloudflare `1015` error.
+If you block requests due to a [rate limiting rule](/waf/rate-limiting-rules/) and you do not configure a [custom error rule](/rules/custom-errors/create-rules/#create-a-custom-error-rule-dashboard) or a [WAF custom response](/waf/rate-limiting-rules/create-zone-dashboard/#configure-a-custom-response-for-blocked-requests) for blocked requests, affected visitors will get your **429 Errors** page displaying a Cloudflare `1015` error.
 
 If you block countries or IP addresses with a firewall rule (now deprecated), affected visitors will get your **1000 Class Errors** page.