Some updates based on latest UI

Author: pedrosousa

src/content/docs/waf/custom-rules/skip/options.mdx

@@ -36,15 +36,15 @@ The available skip options in custom rules are the following:
 
   - Skips specific security products that are not based on the Ruleset Engine. The products you can skip are the following:
 
-  - | Product name in the dashboard                                                        | API value       |
-    | ------------------------------------------------------------------------------------ | --------------- |
-    | [Zone Lockdown](/waf/tools/zone-lockdown/)                                           | `zoneLockdown`  |
-    | [User Agent Blocking](/waf/tools/user-agent-blocking/)                               | `uaBlock`       |
-    | [Browser Integrity Check](/waf/tools/browser-integrity-check/)                       | `bic`           |
-    | [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)                   | `hot`           |
-    | [Security Level](/waf/tools/security-level/)                                         | `securityLevel` |
-    | [Rate Limiting (previous version)](/waf/reference/legacy/old-rate-limiting/)         | `rateLimit`     |
-    | [WAF managed rules (previous version)](/waf/reference/legacy/old-waf-managed-rules/) | `waf`           |
+  - | Product name in the dashboard                                                      | API value       |
+    | ---------------------------------------------------------------------------------- | --------------- |
+    | [Zone Lockdown](/waf/tools/zone-lockdown/)                                         | `zoneLockdown`  |
+    | [User Agent Blocking](/waf/tools/user-agent-blocking/)                             | `uaBlock`       |
+    | [Browser Integrity Check](/waf/tools/browser-integrity-check/)                     | `bic`           |
+    | [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/)                 | `hot`           |
+    | [Security Level](/waf/tools/security-level/)                                       | `securityLevel` |
+    | [Rate limiting rules (Previous version)](/waf/reference/legacy/old-rate-limiting/) | `rateLimit`     |
+    | [Managed rules (Previous version)](/waf/reference/legacy/old-waf-managed-rules/)   | `waf`           |
 
   - The API values are case-sensitive.
 

src/content/docs/waf/detections/firewall-for-ai.mdx

@@ -61,7 +61,7 @@ The PII category for this request would be `EMAIL_ADDRESS`.
 
 Then, use [Security Analytics](/waf/analytics/security-analytics/) in the new application security dashboard to validate that the WAF is correctly detecting prompts leaking PII data in incoming requests. Filter data by the `cf-llm` managed endpoint label and review the detection results on your traffic.
 
-Alternatively, create a WAF custom rule like the one described in the next step using a _Log_ action. This rule will generate [security events](/waf/analytics/security-events/) that will allow you to validate your configuration.
+Alternatively, create a custom rule like the one described in the next step using a _Log_ action. This rule will generate [security events](/waf/analytics/security-events/) that will allow you to validate your configuration.
 
 ### 3. Mitigate requests containing PII
 

src/content/docs/waf/detections/leaked-credentials/get-started.mdx

@@ -117,7 +117,7 @@ To check for leaked credentials in a way that is not covered by the default conf
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Under **Leaked credentials detection** > **Configurations**, select the edit icon.
+3. Under **Leaked Credential Detection** > **Configurations**, select the edit icon.
 4. Select **Add custom username and password location**.
 5. In **Username location** and **Password location** (optional), enter expressions for obtaining the username and the password from the HTTP request. For example, you could use the following expressions:
 

src/content/docs/waf/detections/malicious-uploads/get-started.mdx

@@ -26,7 +26,7 @@ WAF content scanning is available to customers on an Enterprise plan with a paid
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Malicious upload detection**, set the toggle to **On**.
+3. Next to **Malicious uploads detection**, set the toggle to **On**.
 
 </TabItem> <TabItem label="API">
 
@@ -64,6 +64,8 @@ If you use the Expression Editor, enter the following expression:
 (cf.waf.content_scan.has_malicious_obj)
 ```
 
+Rule action: _Block_
+
 This rule will match requests where Cloudflare detects a suspicious or malicious content object. For a list of fields provided by WAF content scanning, refer to [Content scanning fields](/waf/detections/malicious-uploads/#content-scanning-fields).
 
 <Details header="Optional: Combine with other Rules language fields">
@@ -126,14 +128,15 @@ To check uploaded content in a way that is not covered by the default configurat
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Under **Malicious upload detection** > **Configurations**, select the edit icon.
-4. In **Content location**, enter your custom scan expression. For example:
+3. Under **Malicious uploads detection** > **Configurations**, select the edit icon.
+4. Select **Add content location**.
+5. In **Content location**, enter your custom scan expression. For example:
 
    ```txt
    lookup_json_string(http.request.body.raw, "file")
    ```
 
-5. Select **Save**.
+6. Select **Save**.
 
 </TabItem> <TabItem label="API">
 

src/content/docs/waf/get-started.mdx

@@ -72,9 +72,9 @@ If you are an Enterprise customer, do the following:
 
    - **If incoming requests match**:
 
-     | Field        | Operator  | Value |
-     | ------------ | --------- | ----- |
-     | Attack Score | less than | `20`  |
+     | Field            | Operator  | Value |
+     | ---------------- | --------- | ----- |
+     | WAF Attack Score | less than | `20`  |
 
    - **Choose action**: Block
 
@@ -173,7 +173,7 @@ Create a rate limiting rule to [apply rate limiting on a login endpoint](/waf/ra
 
 ### Prevent credential stuffing attacks
 
-Use [leaked credential checks](/waf/managed-rules/check-for-exposed-credentials/) to prevent <GlossaryTooltip term="credential stuffing" link="https://www.cloudflare.com/learning/bots/what-is-credential-stuffing/">credential stuffing</GlossaryTooltip> attacks on your applications.
+Use [leaked credentials detection](/waf/detections/leaked-credentials/) to prevent <GlossaryTooltip term="credential stuffing" link="https://www.cloudflare.com/learning/bots/what-is-credential-stuffing/">credential stuffing</GlossaryTooltip> attacks on your applications.
 
 ### Prevent users from uploading malware into your applications
 

src/content/docs/waf/rate-limiting-rules/create-zone-dashboard.mdx

@@ -28,7 +28,7 @@ import { Render, Tabs, TabItem } from "~/components";
 
 6. (Optional) Under **Cache status**, disable **Also apply rate limiting to cached assets** to consider only the requests that reach the origin when determining the rate.
 
-7. Under **With the same characteristics**, add one or more characteristics that will define the request counters for rate limiting purposes. Each value combination will have its own counter to determine the rate. Refer to [How Cloudflare determines the request rate](/waf/rate-limiting-rules/request-rate/) for more information.
+7. Under **With the same characteristics**, add one or more [characteristics](/waf/rate-limiting-rules/parameters/#with-the-same-characteristics) that will define the request counters for rate limiting purposes. Each value combination will have its own counter to determine the rate. For more information, refer to [How Cloudflare determines the request rate](/waf/rate-limiting-rules/request-rate/).
 
 8. (Optional) To define an expression that specifies the conditions for incrementing the rate counter, enable **Use custom counting expression** and set the expression. By default, the counting expression is the same as the rule expression. The counting expression can include [response fields](/ruleset-engine/rules-language/fields/reference/?field-category=Response).
 

src/content/docs/waf/rate-limiting-rules/find-rate-limit.mdx

@@ -78,7 +78,7 @@ Answering the following questions during your adjustments can help you with your
 
 ### 4. Create a rate limiting rule
 
-1. Select **Create rate limit rule** to go to the [rate limiting creation page](/waf/rate-limiting-rules/create-zone-dashboard/) with your filters, characteristics, and selected rate limit pre-populated.
+1. In the **Request rate analysis** tab, select **Create rate limit rule** to go to the [rate limiting creation page](/waf/rate-limiting-rules/create-zone-dashboard/) with your filters, characteristics, and selected rate limit pre-populated.
 
 2. Select the rule action. Depending on your needs, you can set the rule to log, challenge, or block requests exceeding the selected threshold.
 

src/content/partials/waf/leaked-credentials-detection-enable.mdx

@@ -16,7 +16,7 @@ On Free plans, the leaked credentials detection is enabled by default, and no ac
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
 2. Go to **Security** > **Settings** and filter by **Detections**.
-3. Next to **Leaked credentials detection**, set the toggle to **On**.
+3. Next to **Leaked Credential Detection**, set the toggle to **On**.
 
 </TabItem> <TabItem label="API">