docs(cache): expand dashboard steps, fix headings, align UI labels, remove em dashes

Author: tkornhammar

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

@@ -184,7 +184,7 @@ These examples demonstrate all the available actions in Cache Response Rules usi
 
 </Details>
 
-<Details header="Example: Multiple rules — strip headers, tag responses, and set cache control">
+<Details header="Example: Multiple rules with strip headers, tag responses, and set cache control">
 
 <APIRequest
   path="/zones/{zone_id}/rulesets/phases/http_response_cache_settings/entrypoint"

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

@@ -26,7 +26,20 @@ import { Render, DashButton } from "~/components";
    :::
 
 7. Following the selection of the field and operator, enter the corresponding value that will trigger the Cache Response Rule. For example, if the selected field is `Hostname` and the operator is `equals`, a value of `example.com` would mean the rule matches any request to that hostname.
-8. Under **Then**, select the action you want to apply. Refer to [Available settings](/cache/how-to/cache-response-rules/settings/#available-actions) for the list of available actions and their parameters.
+8. Under **Then**, select one of the following actions:
+
+   - **Modify cache-control directives**: Set or remove `Cache-Control` directives sent by your origin. For each directive, choose **Set directive** or **Remove directive**. For duration-based directives like `max-age` or `s-maxage`, enter a value in seconds. Turn on **Cloudflare only** to apply the directive only within Cloudflare's cache without changing what visitors receive. Refer to [Supported directives](/cache/how-to/cache-response-rules/settings/#supported-directives) for the full list.
+
+   - **Modify cache tags**: Add, override, or remove cache tags on the response for targeted [purging](/cache/how-to/purge-cache/purge-by-tags/). Select one of the following operations:
+     - **Add to existing tags**: Append new tags to the current set.
+     - **Override existing tags**: Replace all current tags with the specified tags.
+     - **Remove from existing tags**: Remove specific tags from the current set.
+
+     For the tag source, you can either specify tags manually or select **Parse from response header** to extract tags from a response header value. When parsing from a header, you can split the header value using a custom separator (for example, commas instead of spaces).
+
+   - **Strip headers**: Remove `Set-Cookie`, `ETag`, or `Last-Modified` headers from the origin response before Cloudflare evaluates the response for caching. Select which headers to strip.
+
+   For more details on each action, refer to [Available settings](/cache/how-to/cache-response-rules/settings/#available-actions).
 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.
 10. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
 

src/content/docs/cache/how-to/cache-response-rules/index.mdx

@@ -11,9 +11,9 @@ Cache Response Rules allow you to configure cache settings based on request and
 
 With Cache Response Rules you can:
 
-- Strip specific headers (ETags, Set-Cookie, Last-Modified) from origin responses before caching.
-- Add, remove, or set cache tags on responses for targeted [cache purging](/cache/how-to/purge-cache/).
-- Modify Cache-Control header directives in the origin response.
+- Modify `Cache-Control` directives sent by your origin.
+- Modify cache tags on responses for targeted [cache purging](/cache/how-to/purge-cache/).
+- Strip headers (`ETag`, `Set-Cookie`, `Last-Modified`) from origin responses before caching.
 
 Cache Response Rules apply to both cached and non-cached (dynamic) responses from the origin. For example, you can strip Set-Cookie headers from responses that are not eligible for caching.
 

src/content/docs/cache/how-to/cache-response-rules/settings.mdx

@@ -69,6 +69,7 @@ The following functions are available in this phase:
 - starts_with
 - substring
 - to_string
+- upper
 - url_decode
 - wildcard_replace
 
@@ -162,7 +163,7 @@ Refer to [Create a rule via API](/cache/how-to/cache-response-rules/create-api/)
 
 Modifies Cache-Control header directives in the origin response.
 
-### Supported directives
+#### Supported directives
 
 **Directives with duration value (seconds):**
 
@@ -186,11 +187,11 @@ Modifies Cache-Control header directives in the origin response.
 - `public`
 - `immutable`
 
-### Directive configuration
+#### Directive configuration
 
 The available parameters depend on the directive type.
 
-#### Directives with duration value
+##### Directives with duration value
 
 Applies to `max-age`, `s-maxage`, `stale-if-error`, and `stale-while-revalidate`.
 
@@ -200,7 +201,7 @@ Applies to `max-age`, `s-maxage`, `stale-if-error`, and `stale-while-revalidate`
 | `cloudflare_only` | Boolean | When enabled, this setting only affects how Cloudflare caches your content. Your visitors still receive the original directive. |
 | `value` | Integer | Duration in seconds. **Required when operation is `set`.** |
 
-#### Directives with optional qualifiers
+##### Directives with optional qualifiers
 
 Applies to `private` and `no-cache`.
 
@@ -210,7 +211,7 @@ Applies to `private` and `no-cache`.
 | `cloudflare_only` | Boolean | When enabled, this setting only affects how Cloudflare caches your content. Your visitors still receive the original directive. |
 | `qualifiers` | Array | Optional list of header names to qualify the directive. |
 
-#### Boolean directives
+##### Boolean directives
 
 Applies to `no-store`, `no-transform`, `must-revalidate`, `proxy-revalidate`, `must-understand`, `public`, and `immutable`.
 

src/content/docs/cache/how-to/cache-response-rules/terraform-example.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 5
 head:
   - tag: title
-    content: Cache Response Rules — Terraform example
+    content: Cache Response Rules Terraform example
 ---
 
 import { Details, Render } from "~/components";