[Several docs] Remove trailing spaces in partial files (#19967)

Author: vil02

src/content/partials/analytics/network-analytics-requirements.mdx

@@ -9,5 +9,5 @@ Network Analytics requires the following:
 
 * A Cloudflare Enterprise plan.
 * Cloudflare Magic Transit or Spectrum.
-* Cloudflare Magic WAN. 
+* Cloudflare Magic WAN.
   :::

src/content/partials/api-shield/label-methodology.mdx

@@ -4,6 +4,6 @@
 ---
 
 | Description | 2xx response codes | 4xx, 5xx response codes |
-| --- | --- | --- | 
+| --- | --- | --- |
 | If all requests are missing authentication, Cloudflare will apply the label: | `cf-missing-auth` | Without successful responses, no label will be added. |
 | If only some requests are missing authentication, Cloudflare will apply the label: | `cf-mixed-auth` | Without successful responses, no label will be added. |

src/content/partials/api-shield/mtls-api-shield-support.mdx

@@ -5,5 +5,5 @@
 
 :::note
 
-While API Shield is not required to use mTLS, many teams may use mTLS to protect their APIs. 
+While API Shield is not required to use mTLS, many teams may use mTLS to protect their APIs.
 :::

src/content/partials/api-shield/routing-path-variables.mdx

@@ -5,5 +5,5 @@
 
 :::note
 
-You can reorder path variables if they are present. For example, you can route `/api/{var1}/users/{var2}` to `/{var2}/users/{var1}`. Segments of the path that are not variables may be added or omitted entirely. 
+You can reorder path variables if they are present. For example, you can route `/api/{var1}/users/{var2}` to `/{var2}/users/{var1}`. Segments of the path that are not variables may be added or omitted entirely.
 :::

src/content/partials/api-shield/set-up-session-identifiers.mdx

@@ -12,7 +12,7 @@
 :::note
 The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected.
 
-If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/configure/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information. 
+If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/configure/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information.
 :::
 
 6. Enter the name of the session identifier.

src/content/partials/bots/ai-bots-definition.mdx

@@ -3,7 +3,7 @@
 
 ---
 
-You can block artificial intelligence (AI) bots, crawlers, and scrapers from scraping your website content and training large language models (LLM) to recreate it without your permission. 
+You can block artificial intelligence (AI) bots, crawlers, and scrapers from scraping your website content and training large language models (LLM) to recreate it without your permission.
 
 When you enable this feature, all verified bots that are classified as AI Search, AI Assistant, AI Crawler, or an Archiver, as well as a number of unverified bots that fall into the [verified bot categories](/bots/reference/verified-bot-categories/) are blocked. It does not block verified bots that fall into the Search Engine categories.
 
@@ -19,11 +19,11 @@ When you enable this feature via a pre-configured managed rule, Cloudflare can d
 
 The rule to block AI bots takes precedence over all other Super Bot Fight Mode rules. For example, if you have enabled **Block AI bots** and **Allow verified bots**, verified AI bots will also be blocked even if you allow other verified bots on your website or application.
 
-For Bot Management customers, if you have set a rule to serve managed challenges to definitely automated bots, AI bots will also be challenged because custom rules run in a phase before Super Bot Fight Mode, which is the phase when the rule to block AI bots runs. 
+For Bot Management customers, if you have set a rule to serve managed challenges to definitely automated bots, AI bots will also be challenged because custom rules run in a phase before Super Bot Fight Mode, which is the phase when the rule to block AI bots runs.
 
-This behavior remains the same if the setting for verified, definitely automated, and likely bots is set to `block` or `allow`. If you have an action to `allow` for these rules, the request is not matched to any rule and proceeds to the next ruleset phase. Similarly, if the action is set to `block`, they will be blocked in the earlier phase and do not move on to match the AI rule at all. However, when the action is `challenge`, the request matches a rule and therefore will not be matched to any rules after. 
+This behavior remains the same if the setting for verified, definitely automated, and likely bots is set to `block` or `allow`. If you have an action to `allow` for these rules, the request is not matched to any rule and proceeds to the next ruleset phase. Similarly, if the action is set to `block`, they will be blocked in the earlier phase and do not move on to match the AI rule at all. However, when the action is `challenge`, the request matches a rule and therefore will not be matched to any rules after.
 
-For self-serve non-Bot Management customers, all rules for verified, definitely automated, and likely bots run in the phase following the AI bots rule. 
+For self-serve non-Bot Management customers, all rules for verified, definitely automated, and likely bots run in the phase following the AI bots rule.
 
 ```mermaid
 ---

src/content/partials/bots/bfm-change-notice.mdx

@@ -5,5 +5,5 @@
 
 :::caution[Change notice for Super Bot Fight Mode rulesets]
 
-Updating Super Bot Fight Mode rules via the Rulesets API is no longer supported and may cause unexpected behavior if you do so. 
+Updating Super Bot Fight Mode rules via the Rulesets API is no longer supported and may cause unexpected behavior if you do so.
 :::

src/content/partials/bots/block-ai-bots-enable.mdx

@@ -5,7 +5,7 @@ inputParameters: param1
 
 import { Markdown } from "~/components"
 
-To block [AI bots](/bots/concepts/bot/#ai-bots): 
+To block [AI bots](/bots/concepts/bot/#ai-bots):
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
 2. Go to **Security** > **Bots**.

src/content/partials/bots/cf-clearance-cookie.mdx

@@ -5,7 +5,7 @@
 
 :::note
 
-[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie. 
+[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie.
 
 The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes.
 :::

src/content/partials/bots/corporate_proxy.mdx

@@ -8,8 +8,8 @@ The Bot Management Corporate Proxy field contains identified cloud-based corpora
 You can access the Corporate Proxy field in [custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), or [Workers](/workers/) to provide different security rules for traffic from these sources. You can also exempt them from rules using Bot Management scores.
 
 ```txt title="Example"
-not cf.bot_management.verified_bot 
-and not cf.bot_management.static_resource 
+not cf.bot_management.verified_bot
+and not cf.bot_management.static_resource
 and not  cf.bot_management.corporate_proxy
 and cf.bot_management.score lt 30
 ```