[Rules, Cache] Mention templates in dashboard instructions

src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx

@@ -6,39 +6,38 @@ sidebar:
 head:
   - tag: title
     content: Create a cache rule in the dashboard
-
 ---
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Caching** > **Cache Rules**.
-3. To create a new empty rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**.
-4. Enter a descriptive name for the rule in **Rule name**.
-5. Under **When incoming requests match**, select **All incoming requests** if you want the rule to apply to all traffic or **Custom filter expression** if you want the rule to only apply to traffic matching the custom expression.
-6. If you selected **Custom filter expression**, under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder). Use the **Field** drop-down list to choose an HTTP property and select an **Operator**. Refer to [Available settings](/cache/how-to/cache-rules/settings/) for the list of available fields and operators.
-
-<div class="medium-img">
+1.  Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
+2.  Go to **Caching** > **Cache Rules**.
+3.  To create a new empty rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**.
+4.  (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
+5.  Enter a descriptive name for the rule in **Rule name**.
+6.  Under **When incoming requests match**, select **All incoming requests** if you want the rule to apply to all traffic or **Custom filter expression** if you want the rule to only apply to traffic matching the custom expression.
+7.  If you selected **Custom filter expression**, under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder). Use the **Field** drop-down list to choose an HTTP property and select an **Operator**. Refer to [Available settings](/cache/how-to/cache-rules/settings/) for the list of available fields and operators.
 
-![Select fields in the Expression Builder.](~/assets/images/cache/select-fields.png)
+    <div class="medium-img">
 
-</div>
+    ![Select fields in the Expression Builder.](~/assets/images/cache/select-fields.png)
 
-6. Following the selection of the field and operator, enter the corresponding value that will trigger the Cache Rule. For example, if the selected field is `Hostname` and the operator is `equals`, a value of `cloudflare.com` would mean the rule matches any request to that hostname.
+    </div>
 
-<div class="medium-img">
+8.  Following the selection of the field and operator, enter the corresponding value that will trigger the Cache Rule. For example, if the selected field is `Hostname` and the operator is `equals`, a value of `cloudflare.com` would mean the rule matches any request to that hostname.
 
-![Example rule](~/assets/images/cache/example-rule.png)
+    <div class="medium-img">
 
-</div>
+    ![Example rule](~/assets/images/cache/example-rule.png)
 
-:::note
+    </div>
 
-Rules can be further customized by using the **Edit expression** option. You can find more information in [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/). 
-:::
+    :::note
+    Rules can be further customized by using the **Edit expression** option. You can find more information in [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).
+    :::
 
-7. Under **Then**, in the **Cache eligibility** section, select [**Bypass cache**](/cache/how-to/cache-rules/settings/#bypass-cache) if you want matching requests to not be cacheable, or **Eligible for cache** if you want Cloudflare to attempt to cache them. Note that [cache-control headers](/cache/concepts/cache-control/) can also impact cache eligibility.
+9.  Under **Then**, in the **Cache eligibility** section, select [**Bypass cache**](/cache/how-to/cache-rules/settings/#bypass-cache) if you want matching requests to not be cacheable, or **Eligible for cache** if you want Cloudflare to attempt to cache them. Note that [cache-control headers](/cache/concepts/cache-control/) can also impact cache eligibility.
 
-8. If you selected **Eligible for cache** in the previous step, you can customize the options described in the [Available settings](/cache/how-to/cache-rules/settings/) section.
+10. If you selected **Eligible for cache** in the previous step, you can customize the options described in the [Available settings](/cache/how-to/cache-rules/settings/) section.
 
-9. Under **Place at**, from the dropdown, you can select the order of your rule. From the main page, you can also change the order of the rules you have created.
+11. Under **Place at**, from the dropdown, you can select the order of your rule. From the main page, you can also change the order of the rules you have created.
 
-10. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+12. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.

src/content/docs/rules/configuration-rules/create-dashboard.mdx

@@ -6,14 +6,14 @@ sidebar:
 head:
   - tag: title
     content: Create a configuration rule in the dashboard
-
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Configuration Rules**.
 3. To create a new empty rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**.
-4. Enter a descriptive name for the rule in **Rule name**.
-5. Under **When incoming requests match**, select if you wish to apply the rule to all incoming requests or only to requests that match a custom filter expression.
-6. (Optional) To define a custom expression, use the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**) or manually enter an expression using the Expression Editor. For more information, refer to [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).
-7. Under **Then the settings are**, add the [configuration settings](/rules/configuration-rules/settings/) you wish to change for requests matching the rule expression.
-8. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
+5. Enter a descriptive name for the rule in **Rule name**.
+6. Under **When incoming requests match**, select if you wish to apply the rule to all incoming requests or only to requests that match a custom filter expression.
+7. (Optional) To define a custom expression, use the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**) or manually enter an expression using the Expression Editor. For more information, refer to [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).
+8. Under **Then the settings are**, add the [configuration settings](/rules/configuration-rules/settings/) you wish to change for requests matching the rule expression.
+9. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.

src/content/docs/rules/origin-rules/create-dashboard.mdx

@@ -6,13 +6,13 @@ sidebar:
 head:
   - tag: title
     content: Create an origin rule in the dashboard
-
 ---
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Origin Rules**.
 3. To create a new empty rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**.
-4. Enter a descriptive name for the rule in **Rule name**.
-5. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/).
-6. Under **Set origin parameters**, define the [origin rule settings](/rules/origin-rules/features/) you wish to change for requests matching the rule expression.
-7. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
+5. Enter a descriptive name for the rule in **Rule name**.
+6. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/).
+7. Under **Set origin parameters**, define the [origin rule settings](/rules/origin-rules/features/) you wish to change for requests matching the rule expression.
+8. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.

src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx

@@ -13,8 +13,9 @@ import { Render } from "~/components";
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Redirect Rules**.
 3. To create a new empty redirect rule, select **Create rule**. To duplicate an existing rule, select the three dots next to it > **Duplicate**.
-4. Enter a descriptive name for the rule in **Rule name**.
-5. Under **When incoming requests match**, select one of the following options:
+4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
+5. Enter a descriptive name for the rule in **Rule name**.
+6. Under **When incoming requests match**, select one of the following options:
    - **Wildcard pattern**: The rule will only apply to traffic matching the wildcard pattern.
      - **Request URL**: Enter the [wildcard pattern](/ruleset-engine/rules-language/operators/#wildcard-matching) using the asterisk (`*`) character to match multiple requests. For example, `https://*.example.com/files/*`.
      - **Then**: Define the [URL redirect settings](/rules/url-forwarding/single-redirects/settings/) including:
@@ -25,7 +26,7 @@ import { Render } from "~/components";
      - **Then**: Define the [URL redirect settings](/rules/url-forwarding/single-redirects/settings/) for all incoming requests.
    - **Custom filter expression**: The rule will only apply to traffic matching a custom expression. Define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/) to configure which requests should be redirected.
      - **Then**: Define the [URL redirect settings](/rules/url-forwarding/single-redirects/settings/) for requests matching the custom rule expression.
-6. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+7. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
 
 <Render
 	file="url-forwarding/requires-proxied-site"