[WAF] Update page titles (#25120)

Author: pedrosousa

src/content/docs/waf/managed-rules/check-for-exposed-credentials/configure-api.mdx

@@ -1,11 +1,9 @@
 ---
 pcx_content_type: how-to
-title: Configure via API
+title: Configure exposed credentials checks via API
 sidebar:
   order: 4
-head:
-  - tag: title
-    content: Configure exposed credentials checks via API
+  label: Configure via API
 ---
 
 import { Render, APIRequest } from "~/components";

src/content/docs/waf/managed-rules/check-for-exposed-credentials/configure-terraform.mdx

@@ -1,11 +1,9 @@
 ---
-title: Configure with Terraform
+title: Configure exposed credentials checks using Terraform
 pcx_content_type: configuration
 sidebar:
   order: 5
-head:
-  - tag: title
-    content: Configure Exposed Credentials Check using Terraform
+  label: Configure using Terraform
 ---
 
 import { Render } from "~/components";

src/content/docs/waf/managed-rules/check-for-exposed-credentials/how-checks-work.mdx

@@ -1,11 +1,9 @@
 ---
 pcx_content_type: concept
-title: How it works
+title: How exposed credentials checks work
 sidebar:
   order: 2
-head:
-  - tag: title
-    content: How exposed credentials checks work
+  label: How it works
 ---
 
 import { Render, Example } from "~/components";

src/content/docs/waf/managed-rules/check-for-exposed-credentials/test-configuration.mdx

@@ -1,11 +1,9 @@
 ---
 pcx_content_type: reference
-title: Test your configuration
+title: Test your exposed credentials checks configuration
 sidebar:
   order: 6
-head:
-  - tag: title
-    content: Test your exposed credentials checks configuration
+  label: Test your configuration
 ---
 
 import { Render } from "~/components";

src/content/docs/waf/rate-limiting-rules/use-cases.mdx

@@ -1,11 +1,9 @@
 ---
-title: Rule examples
+title: Rate limiting rule examples
 pcx_content_type: configuration
 sidebar:
   order: 20
-head:
-  - tag: title
-    content: Rate limiting rule examples
+  label: Rule examples
 ---
 
 import { Example } from "~/components";

src/content/docs/waf/reference/alerts.mdx

@@ -1,8 +1,9 @@
 ---
-title: Alerts
+title: Alerts for security events
 pcx_content_type: reference
 sidebar:
   order: 1
+  label: Alerts
 ---
 
 import { AvailableNotifications } from "~/components";

src/content/docs/waf/reference/legacy/old-rate-limiting/troubleshooting.mdx

@@ -1,31 +1,28 @@
 ---
 pcx_content_type: troubleshooting
 source: https://support.cloudflare.com/hc/en-us/articles/115000546328-Troubleshooting-Cloudflare-Rate-Limiting
-title: Troubleshooting
+title: Troubleshoot Rate Limiting (previous version)
 sidebar:
   order: 2
-head:
-  - tag: title
-    content: Troubleshoot Rate Limiting (previous version)
+  label: Troubleshooting
 noindex: true
 ---
 
 A few common rate limiting configuration issues prevent proper request matches:
 
-* **Including HTTP or HTTPS protocol schemes in rule patterns** (such as `https://example.com/*`). To restrict rules to match only HTTP or HTTPS traffic, use the schemes array in the request match. For example, `"schemes": [ "HTTPS" ]`.
-* **Forgetting a trailing slash character (`/`)**. Cloudflare Rate Limiting only treats requests for the homepage (such as `example.com` and `example.com/`) as equivalent, but not any other path (such as `example.com/path/` and `example.com/path`). To match request paths both with and without the trailing slash, use a wildcard match (for example, `example.com/path*`).
-* **Including a query string or anchor** (such as `example.com/path?foo=bar` or `example.com/path#section1`). A rule like `example.com/path` will match requests for `example.com/path?foo=bar`.
-* **Overriding a rate limit with [IP Access rules](/waf/tools/ip-access-rules/)**.
-* **Including a port number** (such as `example.com:8443/api/`). Rate Limiting does not consider port numbers within rules. Remove the port number from the URL so that the rate limit rule triggers as expected.
+- **Including HTTP or HTTPS protocol schemes in rule patterns** (such as `https://example.com/*`). To restrict rules to match only HTTP or HTTPS traffic, use the schemes array in the request match. For example, `"schemes": [ "HTTPS" ]`.
+- **Forgetting a trailing slash character (`/`)**. Cloudflare Rate Limiting only treats requests for the homepage (such as `example.com` and `example.com/`) as equivalent, but not any other path (such as `example.com/path/` and `example.com/path`). To match request paths both with and without the trailing slash, use a wildcard match (for example, `example.com/path*`).
+- **Including a query string or anchor** (such as `example.com/path?foo=bar` or `example.com/path#section1`). A rule like `example.com/path` will match requests for `example.com/path?foo=bar`.
+- **Overriding a rate limit with [IP Access rules](/waf/tools/ip-access-rules/)**.
+- **Including a port number** (such as `example.com:8443/api/`). Rate Limiting does not consider port numbers within rules. Remove the port number from the URL so that the rate limit rule triggers as expected.
 
 ## Common API errors
 
-The following common errors may prevent configuring rate limiting rules via the [Cloudflare API](/api/resources/rate_limits/methods/create/):  
+The following common errors may prevent configuring rate limiting rules via the [Cloudflare API](/api/resources/rate_limits/methods/create/):
 
-* `Decoding is not yet implemented` – Indicates that your request is missing the `Content-Type: application/json` header. Add the header to your API request to fix the issue.
-* `Ratelimit.api.not_entitled` – Enterprise customers must contact their account team before adding rules.
+- `Decoding is not yet implemented` – Indicates that your request is missing the `Content-Type: application/json` header. Add the header to your API request to fix the issue.
+- `Ratelimit.api.not_entitled` – Enterprise customers must contact their account team before adding rules.
 
 :::note
-
 The `origin_traffic` parameter can only be set on Enterprise plans. Setting `"origin_traffic" = false` for a rule on a Free, Pro, or Business domain is automatically converted into `"origin_traffic" = true`.
 :::

src/content/docs/waf/reference/legacy/old-waf-managed-rules/troubleshooting.mdx

@@ -1,55 +1,52 @@
 ---
 pcx_content_type: troubleshooting
 source: https://support.cloudflare.com/hc/en-us/articles/200172016-Understanding-WAF-managed-rules-Web-Application-Firewall-
-title: Troubleshooting
+title: Troubleshoot WAF managed rules (previous version)
 sidebar:
   order: 2
-head:
-  - tag: title
-    content: Troubleshoot WAF managed rules (previous version)
+  label: Troubleshooting
 noindex: true
 ---
 
 By default, WAF managed rules are fully managed via the Cloudflare dashboard and are compatible with most websites and web applications. However, false positives and false negatives may occur:
 
-* **False positives**: Legitimate requests detected and filtered as malicious.
-* **False negatives**: Malicious requests not filtered.
+- **False positives**: Legitimate requests detected and filtered as malicious.
+- **False negatives**: Malicious requests not filtered.
 
 ## Troubleshoot false positives
 
 The definition of suspicious content is subjective for each website. For example, PHP code posted to your website is normally suspicious. However, your website may be teaching how to code and it may require PHP code submissions from visitors. In this situation, you should disable related managed rules for this website, since they would interfere with normal website operation.
 
-To test for false positives, set WAF managed rules to *Simulate* mode. This mode allows you to record the response to possible attacks without challenging or blocking incoming requests. Also, review the Security Events' [sampled logs](/waf/analytics/security-events/#sampled-logs) to determine which managed rules caused false positives.
+To test for false positives, set WAF managed rules to _Simulate_ mode. This mode allows you to record the response to possible attacks without challenging or blocking incoming requests. Also, review the Security Events' [sampled logs](/waf/analytics/security-events/#sampled-logs) to determine which managed rules caused false positives.
 
 If you find a false positive, there are several potential resolutions:
 
-* **Add the client’s IP addresses to the [IP Access Rules](/waf/tools/ip-access-rules/) allowlist:** If the browser or client visits from the same IP addresses, allowing is recommended.
-* **Disable the corresponding managed rule(s)**: Stops blocking or challenging false positives, but reduces overall site security. A request blocked by Rule ID `981176` refers to OWASP rules. Decrease OWASP sensitivity to resolve the issue.
-* **Bypass WAF managed rules with a firewall rule (deprecated):** [Create a firewall rule](/firewall/cf-dashboard/create-edit-delete-rules/#create-a-firewall-rule) with the *Bypass* action to deactivate WAF managed rules for a specific combination of parameters. For example, [bypass managed rules](/firewall/cf-firewall-rules/actions/) for a specific URL and a specific IP address or user agent.
-* **(Not recommended) Disable WAF managed rules for traffic to a URL:** Lowers security on the particular URL endpoint. Configured via [Page Rules](/rules/page-rules/).
+- **Add the client’s IP addresses to the [IP Access Rules](/waf/tools/ip-access-rules/) allowlist:** If the browser or client visits from the same IP addresses, allowing is recommended.
+- **Disable the corresponding managed rule(s)**: Stops blocking or challenging false positives, but reduces overall site security. A request blocked by Rule ID `981176` refers to OWASP rules. Decrease OWASP sensitivity to resolve the issue.
+- **Bypass WAF managed rules with a firewall rule (deprecated):** [Create a firewall rule](/firewall/cf-dashboard/create-edit-delete-rules/#create-a-firewall-rule) with the _Bypass_ action to deactivate WAF managed rules for a specific combination of parameters. For example, [bypass managed rules](/firewall/cf-firewall-rules/actions/) for a specific URL and a specific IP address or user agent.
+- **(Not recommended) Disable WAF managed rules for traffic to a URL:** Lowers security on the particular URL endpoint. Configured via [Page Rules](/rules/page-rules/).
 
 Additional guidelines are as follows:
 
-* If one specific rule causes false positives, set rule’s **Mode** to *Disable* rather than turning *Off* the entire rule **Group**.
-* For false positives with the administrator section of your website, create a [page rule](/rules/page-rules/) to **Disable Security** for the admin section of your site resources — for example, `example.com/admin`.
+- If one specific rule causes false positives, set rule’s **Mode** to _Disable_ rather than turning _Off_ the entire rule **Group**.
+- For false positives with the administrator section of your website, create a [page rule](/rules/page-rules/) to **Disable Security** for the admin section of your site resources — for example, `example.com/admin`.
 
 ## Troubleshoot false negatives
 
 To identify false negatives, review the HTTP logs on your origin web server. To reduce false negatives, use the following checklist:
 
-* Are WAF managed rules enabled in **Security** > **WAF** > **Managed rules**?
+- Are WAF managed rules enabled in **Security** > **WAF** > **Managed rules**?
 
-* Are WAF managed rules being disabled via [Page Rules](/rules/page-rules/)?
+- Are WAF managed rules being disabled via [Page Rules](/rules/page-rules/)?
 
-* Not all managed rules are enabled by default, so review individual managed rule default actions.
+- Not all managed rules are enabled by default, so review individual managed rule default actions.
+  - For example, Cloudflare allows requests with empty user agents by default. To block requests with an empty user agent, change the rule **Mode** to _Block_.
+  - Another example: if you are looking to block unmitigated SQL injection attacks, make sure the relevant SQLi rules are enabled and set to _Block_ under the **Cloudflare Specials** group.
 
-  * For example, Cloudflare allows requests with empty user agents by default. To block requests with an empty user agent, change the rule **Mode** to *Block*.
-  * Another example: if you are looking to block unmitigated SQL injection attacks, make sure the relevant SQLi rules are enabled and set to *Block* under the **Cloudflare Specials** group.
+- Are DNS records that serve HTTP traffic proxied through Cloudflare?
 
-* Are DNS records that serve HTTP traffic proxied through Cloudflare?
+- Is a firewall rule [bypassing](/firewall/cf-firewall-rules/actions/#supported-actions) managed rules?
 
-* Is a firewall rule [bypassing](/firewall/cf-firewall-rules/actions/#supported-actions) managed rules?
+- Does an allowed country, ASN, IP range, or IP address in [IP Access rules](/waf/tools/ip-access-rules/) or [firewall rules](/firewall/cf-firewall-rules/) match the attack traffic?
 
-* Does an allowed country, ASN, IP range, or IP address in [IP Access rules](/waf/tools/ip-access-rules/) or [firewall rules](/firewall/cf-firewall-rules/) match the attack traffic?
-
-* Is the malicious traffic reaching your origin IP addresses directly to bypass Cloudflare protection? Block all traffic except from [Cloudflare's IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) at your origin web server.
+- Is the malicious traffic reaching your origin IP addresses directly to bypass Cloudflare protection? Block all traffic except from [Cloudflare's IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) at your origin web server.

src/content/docs/waf/reference/phases.mdx

@@ -1,8 +1,9 @@
 ---
-title: Phases
+title: WAF phases
 pcx_content_type: reference
 sidebar:
   order: 2
+  label: Phases
 tableOfContents: false
 ---
 

src/content/docs/waf/tools/ip-access-rules/actions.mdx

@@ -1,11 +1,9 @@
 ---
-title: Actions
+title: IP Access rules actions
 pcx_content_type: reference
 sidebar:
   order: 4
-head:
-  - tag: title
-    content: IP Access rules actions
+  label: Actions
 ---
 
 An IP Access rule can perform one of the following actions: