Apply suggestions from PCX review

Author: pedrosousa

src/content/docs/rules/reference/page-rules-migration.mdx

@@ -9,18 +9,18 @@ import { Render, TabItem, Tabs, Example } from "~/components";
 
 Cloudflare is continuously improving its platform to deliver more powerful and scalable tools for managing your configurations. To help you take full advantage of these improvements, we recommend using [modern Rules features](/rules/) for new implementations. These products address the limitations of Page Rules while providing greater flexibility, scalability, and ease of use.
 
-For a quick start, explore the one-click templates available in the Rules tab of the dashboard. These templates simplify common configurations like redirects, rewrites and header modifications, making setup faster and easier.
+For a quick start, explore the one-click templates available in the Cloudflare dashboard in **Rules** > **Templates**. These templates simplify common configurations like redirects, rewrites and header modifications, making setup faster and easier.
 
 ## Page Rules migration
 
-To make the transition seamless, Cloudflare will handle the migration of your existing Page Rules automatically. This process is planned for **late 2025 or beyond**, with no action required on your part. You will receive advance notification before any changes are made.
+To make the transition seamless, Cloudflare will handle the migration of your existing Page Rules automatically. This process is planned for late 2025 or beyond, with no action required on your part. You will receive advance notification before any changes are made.
 
 If you wish to explore the benefits of modern Rules features sooner, you can begin adopting them today. Doing so allows you to:
 
 - Take advantage of modern features and capabilities sooner.
 - Customise and refine your rules to match your evolving needs.
 
-To assist with this process, we've provided a comprehensive mapping between Page Rules settings and modern Rules products in this guide.
+To assist with this process, we provide you with a comprehensive mapping between Page Rules settings and modern Rules products in this guide.
 
 ## Why transition?
 
@@ -39,20 +39,20 @@ Improvements in modern Rules features include:
 
 The evaluation and execution order of Rules features is different from Page Rules:
 
-- **Rule matching logic**: Page Rules apply the first matching rule *(first match wins)*. In contrast, modern Rules are stackable, meaning **multiple matching rules** can combine and apply to the same request *(last match wins)*. For example, if multiple Cache Rules match the same URL, the features in those rules will all apply in order.
-- **Action separation**: A Page Rule may include multiple actions for different products that are applied in a **sequence** selected by the customer within the Page Rule itself. Modern Rules features are evaluated [in a fixed sequence](/rules/origin-rules/#execution-order), with customers defining the rule order within a product [phase](/ruleset-engine/reference/phases-list/).
-- **Precedence**: Modern Rules features **take precedence** over Page Rules. For instance, if both define caching settings for the same path, Cache Rules will override Page Rules.
-- **Caching behaviour**: In Cache Rules, selecting *Eligible for cache* automatically enables *Cache Everything* by default. To maintain the exact behaviour of Page Rules, you may need to [adjust your configuration](/cache/how-to/cache-rules/page-rules-migration/).
-- **Interactions with Workers**: Requests handled by Workers will suppress Page Rules actions, but they **will not suppress** actions from modern Rules features.
+- **Rule matching logic**: Page Rules apply the first matching rule (first match wins). In contrast, modern Rules are stackable, meaning multiple matching rules can combine and apply to the same request (last match wins). For example, if multiple cache rules match the same URL, the features in those rules will all apply in order.
+- **Action separation**: A Page Rule may include multiple actions for different products that are applied in a sequence selected by the customer within the Page Rule itself. Modern Rules features are evaluated [in a fixed sequence](/rules/origin-rules/#execution-order), with customers defining the rule order within a product [phase](/ruleset-engine/reference/phases-list/).
+- **Precedence**: Modern Rules features take precedence over Page Rules. For instance, if both define caching settings for the same path, Cache Rules will override Page Rules.
+- **Caching behavior**: In Cache Rules, selecting **Eligible for cache** automatically enables **Cache Everything** by default. To maintain the exact behavior of Page Rules, you may need to [adjust your configuration](/cache/how-to/cache-rules/page-rules-migration/).
+- **Interactions with Workers**: Requests handled by Workers will suppress Page Rules actions, but they will not suppress actions from modern Rules features.
 
 ## Convert Page Rules URLs to filter expressions
 
 Modern Rules use filter expressions instead of URL patterns. These expressions, built with the Rules language, allow greater precision by leveraging [fields](/ruleset-engine/rules-language/fields/), [functions](/ruleset-engine/rules-language/functions/), and [operators](/ruleset-engine/rules-language/operators/).
 
-The following example demonstrates the use of the `http.request.full_uri` [field](/ruleset-engine/rules-language/fields/standard-fields/#httprequestfull_uri) and the `wildcard` operator for [wildcard matching](/ruleset-engine/rules-language/operators/#wildcard-matching):
+The following example demonstrates the use of the [`http.request.full_uri`](/ruleset-engine/rules-language/fields/standard-fields/#httprequestfull_uri) field and the `wildcard` operator for [wildcard matching](/ruleset-engine/rules-language/operators/#wildcard-matching):
 
 <Example>
-A **Page Rules URL** like 
+A **Page Rules URL** like:
 
 `example.com/*/downloads/*.txt` 
 
@@ -64,14 +64,15 @@ becomes a **filter expression** such as:
 [Single Redirects](/rules/url-forwarding/single-redirects/create-dashboard/) and [Rewrite URL](/rules/transform/url-rewrite/create-dashboard/) rules also offer a simplified view called **Wildcard pattern**, allowing you to specify URL patterns (`http*://example.com/*/downloads/*.txt*`) without specifying the full filter expression (`http.request.full_uri wildcard "http*://example.com/*/downloads/*.txt*"`).
 
 ### Important considerations
--  **Protocol scheme**: Page Rules URL matching does not include the URI scheme (for example, `http://` or `https://`) unless explicitly included in the rule. Filter expressions using `http.request.full_uri` field, however, require matching the full URI, including the protocol scheme. To make your filter expression scheme-agnostic, use `http*://` as a wildcard for both `http://` and `https://`.
--  **Query strings**: Page Rules ignore query strings unless they are part of the rule URL. Filter expressions include the query string automatically, as part of the `http.request.full_uri` field. To ensure query strings do not affect your matching, append a `*` wildcard at the end of your filter expression, such as `.txt*`.
+
+- **Protocol scheme**: Page Rules URL matching does not include the URI scheme (for example, `http://` or `https://`) unless explicitly included in the rule. Filter expressions using `http.request.full_uri` field, however, require matching the full URI, including the protocol scheme. To make your filter expression scheme-agnostic, use `http*://` as a wildcard for both `http://` and `https://`.
+- **Query strings**: Page Rules ignore query strings unless they are part of the rule URL. Filter expressions include the query string automatically, as part of the `http.request.full_uri` field. To ensure query strings do not affect your matching, append a `*` wildcard at the end of your filter expression, such as `.txt*`.
 
 ## Feature correspondence table
 
 To help you map existing Page Rules to modern Rules products, this table outlines how Page Rules settings translate to modern Rules and provides examples for common configurations.
 
-Also, to streamline common configurations, the Rules tab in the dashboard now includes dozens of **one-click templates**. These templates enable you to deploy commonly used features — like redirects, rewrites, header modifications and more — instantly, with pre-filled filter expressions and actions. Explore these templates in the dashboard for a faster setup.
+Also, to streamline common configurations, the Cloudflare the dashboard now includes dozens of one-click templates, available in **Rules** > **Templates**. These templates enable you to deploy commonly used features — such as redirects, rewrites, and header modifications — instantly, with pre-filled filter expressions and actions. Explore these templates in the dashboard for a faster setup.
 
 | Page Rules setting          | New implementation uses...           | Migration/Replacement instructions                                          |
 | --------------------------- | ------------------------------------ | --------------------------------------------------------------------------- |