Final formatting changes

Author: pedrosousa

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

@@ -52,7 +52,7 @@ When viewing a ruleset, Cloudflare shows default actions for each rule listed un
 * **Disable**: Turns off the specific rule within the group.
 * **Block**: Discards the request.
 * **Interactive Challenge**: The visitor receives a challenge page that requires interaction.
-* **Simulate**: The request is allowed through but is logged in [**Sampled logs**](/waf/analytics/security-events/#sampled-logs).
+* **Simulate**: The request is allowed through but is logged in [Sampled logs](/waf/analytics/security-events/#sampled-logs).
 
 Cloudflare’s [WAF changelog](/waf/change-log/) allows customers to monitor ongoing changes to the Cloudflare Managed Ruleset.
 
@@ -66,7 +66,7 @@ After OWASP evaluates a request, Cloudflare compares the final score to the **Se
 
 * **Block**: The request is discarded.
 * **Challenge**: The visitor receives an interactive challenge page.
-* **Simulate**: The request is allowed through but is logged in [**Sampled logs**](/waf/analytics/security-events/#sampled-logs).
+* **Simulate**: The request is allowed through but is logged in [Sampled logs](/waf/analytics/security-events/#sampled-logs).
 
 The sensitivity score required to trigger the WAF for a specific **Sensitivity** is as follows:
 
@@ -80,7 +80,7 @@ For AJAX requests, the following scores are applied instead:
 * **Medium**: 80 and higher
 * **High**: 65 and higher
 
-Review the entry in [**Sampled logs**](/waf/analytics/security-events/#sampled-logs) for the final score and for the individual triggered rules.
+Review the entry in [Sampled logs](/waf/analytics/security-events/#sampled-logs) for the final score and for the individual triggered rules.
 
 ### Control the OWASP package
 
@@ -99,7 +99,7 @@ Cloudflare recommends initially setting the sensitivity to *Low* and reviewing f
 
 :::note
 
-**Sampled logs** displays rule ID `981176` when a request is blocked by OWASP. Also, some OWASP rules listed in **Sampled logs** do not appear in the OWASP list of rules because disabling those rules is not recommended.
+Sampled logs displays rule ID `981176` when a request is blocked by OWASP. Also, some OWASP rules listed in Sampled logs do not appear in the OWASP list of rules because disabling those rules is not recommended.
 :::
 
 ***

src/content/docs/waf/reference/migration-guides/waf-managed-rules-migration.mdx

@@ -308,7 +308,7 @@ The returned configuration in the example above, which would match the existing
    }'
    ```
 
-   After invoking this API endpoint, both WAF managed rules and WAF Managed Rules will be enabled. Check [**Sampled logs**](/waf/analytics/security-events/#sampled-logs) in Security Events for any legitimate traffic getting blocked, and perform any required adjustments to the WAF Managed Rules configuration. For example, you can [add an override](/ruleset-engine/managed-rulesets/override-managed-ruleset/) for a single rule that disables it or changes its action.
+   After invoking this API endpoint, both WAF managed rules and WAF Managed Rules will be enabled. Check [Sampled logs](/waf/analytics/security-events/#sampled-logs) in Security Events for any legitimate traffic getting blocked, and perform any required adjustments to the WAF Managed Rules configuration. For example, you can [add an override](/ruleset-engine/managed-rulesets/override-managed-ruleset/) for a single rule that disables it or changes its action.
 
 4. To finish the migration and disable WAF managed rules, set the configuration for the new WAF using the settings you obtained in step 2 and possibly adjusted in step 3. Make sure you include the `waf_migration=pending&phase_two=1` query string parameters.
 

src/content/docs/waf/tools/validation-checks.mdx

@@ -13,7 +13,7 @@ Currently, you cannot disable validation checks. They run early in Cloudflare's
 
 ## Event logs for validation checks
 
-Actions performed by the Validation component appear in the **Sampled logs** of [Security Events](/waf/analytics/security-events/) associated with the `Validation` service and without a rule ID. Event logs downloaded from the API show source as `Validation` and action as `drop` when this behavior occurs.
+Actions performed by the Validation component appear in [Sampled logs](/waf/analytics/security-events/#sampled-logs) in Security Events, associated with the `Validation` service and without a rule ID. Event logs downloaded from the API show source as `Validation` and action as `drop` when this behavior occurs.
 
 The following example shows a request blocked by the Validation component due to a malformed `User-Agent` HTTP request header:
 

src/content/release-notes/waf-general.yaml

@@ -18,7 +18,7 @@ entries:
   - publish_date: "2024-11-14"
     title: Security Events pagination
     description: |-
-      Fixed an issue with pagination in Security Events' **Sampled logs** where some pages were missing data. Also removed the total count from the events log as these are only sampled logs.
+      Fixed an issue with pagination in Security Events' Sampled logs where some pages were missing data. Also removed the total count from the events log as these are only sampled logs.
   - publish_date: "2024-11-04"
     title: New table in Security Analytics and Security Events
     description: |-